Skip to main content
Glama
Sign In
LeadAce

LeadAce

by aitit-inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_master_document

Retrieve a shared master document by its slug to access templates or guidelines for consistent outbound messaging.

Instructions

Get a shared master document by slug.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_master_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesMaster document slug (e.g. "tpl_business", "tpl_email_guidelines")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.7.54

TDQS

A3.5/5.0
Behavior3/5

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

Given no annotations, the description carries the burden of transparency, and 'Get' clearly signals a read-only operation. It adds the qualifier 'shared,' which hints at the resource type, but does not disclose what the response contains, any required permissions, or potential error conditions—adequate for a simple getter but not detailed.

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?

The description is a single, front-loaded sentence with no filler or redundant phrasing. Every word contributes meaning, making it exceptionally concise and easy to parse.

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

Completeness3/5

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

For a one-parameter read operation with no output schema or annotations, the description provides the essential 'what' and 'how.' However, it omits any indication of the returned document structure or format, leaving the agent to infer the response shape—acceptable for a simple tool but not fully complete.

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?

The schema provides 100% coverage for the single 'slug' parameter, including an example, so the description's 'by slug' adds no new semantic information. The description reinforces the parameter's role but does not go beyond what the schema already states, earning the baseline 3.

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

Purpose4/5

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

The description uses a clear verb ('Get') and explicitly names the resource ('shared master document') and retrieval method ('by slug'), which sets it apart from the generic get_document sibling. However, it does not explicitly contrast itself with get_document or list_master_documents, so it stops short of a perfect 5.

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

Usage Guidelines3/5

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

The description implies usage: the agent should call this when a master document's slug is known. It provides no explicit when-not-to-use guidance or reference to alternatives like get_document or list_master_documents, so the context is only implied.

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

Deploy Server

Other Tools