get_consulting_engagementGet one owned engagement with its document revisions, milestones, and internal deliverables. Long document bodies are previewed.
| Name | Required | Description | Default |
|---|---|---|---|
| engagement_id | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations (readOnlyHint, idempotentHint, destructiveHint) indicate safe read. The description adds that long document bodies are previewed, providing useful nuance beyond annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two concise sentences deliver key information without redundancy. Front-loaded with the main action and then additional details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description appropriately focuses on input and behavior. It covers the returned entity structure and the note on long document previews, making it substantially complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter engagement_id is clear from the schema. The description mentions 'owned engagement', hinting at authorization scope, but does not add detailed semantics beyond the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states it retrieves a single engagement along with its related entities (document revisions, milestones, internal deliverables). It explicitly distinguishes from list_consulting_engagements by focusing on a single record.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when you need a specific engagement with its children, but does not explicitly contrast with other retrieval tools like get_deal or provide when-not-to-use guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Every tool targets a distinct resource and action, with detailed descriptions that clearly separate overlapping domains (e.g., consulting vs. marketing vs. outreach). Even within the same domain, tools like 'create_consulting_deliverable' and 'create_consulting_document_revision' are unambiguous due to their specific nouns.
All tools follow a consistent verb_noun snake_case pattern (e.g., 'create_invoice', 'get_deal', 'list_agents'). The few exceptions like 'locus_determine_from_scores' still adhere to the verb_noun structure and do not break the pattern.
With 124 tools, the server is massively over-scoped for typical MCP use. The tool count far exceeds the '50+ extreme mismatch' threshold, making it nearly impossible for an agent to efficiently navigate or select the right tool without extensive context. Even a large platform should consolidate or expose fewer tools.
The tool surface covers CRUD and lifecycle operations across at least 10 domains (sales, consulting, marketing, outreach, accounting, workflows, ticketing, API keys, feedback, platform metrics). Each domain appears to have no obvious gaps—e.g., invoicing includes create, update, send, mark paid, void; ticketing includes create, update, archive, dependencies, batch, scenarios, validation.