Skip to main content
Glama

MisarReach MCP Server

by io.github.Misar-AI

get_pipeline

Read-onlyIdempotent

Get the sales pipeline as a board: deals grouped by stage, with revenue totals.

Use this for 'how does the pipeline look' questions and stage-by-stage review. It is the board view of the same deals list_deals returns flat — reach for that one when you need filtering or paging, since this returns the whole board.

Reads only. Requires an API key. Stages are new, contacted, interested, meeting, proposal, closed and lost. Money is in minor currency units (cents), so divide by 100 before showing it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
workspaceIdNoOptional workspace UUID to filter pipeline

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already mark this as read-only, idempotent, and non-destructive, and the description adds important context beyond that: API key requirement, the exact stage vocabulary, and the critical detail that monetary values are in cents. These details are not present in annotations or schema, enriching behavioral understanding.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence earns its place: the first defines the output, the second gives usage and sibling differentiation, and the third covers critical operational details. It is compact and front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given a simple one-param read-only tool with no output schema, the description fully covers purpose, alternatives, auth, stage values, and currency units. There is no significant gap that would leave an agent guessing about how to invoke or interpret the tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% for the single optional workspaceId parameter, so the schema already documents it. The description adds context that this tool returns the whole board (with workspaceId being the only possible filter), which helps but does not substantially extend the parameter's semantic meaning beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool returns a sales pipeline board with deals grouped by stage and revenue totals. It explicitly distinguishes from the sibling list_deals by framing this as a 'board view' versus a flat list, showing precise resource and scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit when-to-use guidance: 'for how does the pipeline look questions and stage-by-stage review.' It names the alternative tool (list_deals) for filtering/paging needs, making the decision between them unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MisarReach MCP Server toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.3/5.0
Disambiguation5/5

Every tool targets a distinct resource and action: deals, leads, lists, autopilot runs, sales agent config, channels, and discovery. Even where tools share an entity, they are clearly differentiated (e.g., list_deals vs get_pipeline, update_deal vs move_deal_stage), with descriptions explicitly calling out when to use which.

Naming Consistency5/5

All 27 tools follow a strict verb_noun snake_case pattern: create, get, list, update, move, search, score, sync, start, submit, verify, etc. No mixed conventions or vague verbs—each name precisely signals its function.

Tool Count3/5

27 tools is on the heavier side and slightly exceeds the typical well-scoped range. However, the server covers multiple subdomains (deals, lead discovery, autopilot, sales agent, channels), so the count is justified by the breadth of the domain, though it feels dense.

Completeness4/5

Core lifecycles are covered: deals (create, list, update, move), leads (search, sync, list, enrich, score, verify, send), autopilot (start, list, status), sales agent (config, actions, process), and channels (status, update). Minor gaps include no delete tool for deals/leads and no stop-autopilot, but these are likely intentional and not blocking.

Resources