Context Studios MCP

Get Guide

get_guide

Read-only

Get a specific guide.

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_guide"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Exact public slug for a blog post, guide, location page, comparison, glossary term, CMS page, or landing page.
`locale`	No	Preferred content locale. Supported values are de, en, fr, and it. Some source catalogs may fall back to de or en.	en
`responseFormat`	No	Response shape. Use v2 for agent-friendly {success,data,meta,error}; legacy remains available for older clients.	legacy

Output Schema

Name	Required	Description
`data`	No	Structured result payload. Present for responseFormat='v2' tools.
`meta`	No	Result metadata such as count, locale fallback, cache scope, or response format.
`count`	No	Number of returned records for list and search tools.
`error`	No	Human-readable error message when success is false.
`success`	No	Whether the tool call completed successfully.

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 5, 2026

TDQS

C2.5/5.0

Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is covered, but the description adds no behavioral context. It fails to disclose that the slug parameter can point to non-guide content (as shown in the schema), which is surprising given the tool name. No mention of locale fallback or response shape, though these are partially covered by the schema.

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

Conciseness3/5

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

The description is extremely concise (one sentence) and front-loaded, but it is under-specified. It avoids verbosity but fails to earn its place by carrying enough meaning to be useful. It is not as deficient as a pure tautology but lacks necessary detail.

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

Completeness2/5

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

Despite a rich schema and output schema, the description is incomplete for agent decision-making. It offers no usage guidance, no differentiation from siblings, and no indication that the slug is required or that it might apply to content types other than guides. The tool has many siblings, so this lack of context makes it difficult to select correctly.

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% with detailed descriptions, enums, and examples for all three parameters, so the baseline is 3. The description adds no parameter information. The slug description is broader than the tool name suggests, but that is a schema issue, not compensated by the description.

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

Purpose3/5

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

The description 'Get a specific guide' uses a specific verb (get) and resource (guide) and implies a single item, differentiating from list/search tools. However, it is vague and does not mention the slug parameter, and the schema's slug description says it applies to many content types (blog posts, location pages, etc.), creating ambiguity about whether this tool only returns guides.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus alternatives like list_guides, search_guides, get_blog_posts, or get_glossary_term. With many sibling getters, the description should explicitly state that this fetches a single guide by exact slug, but it provides no context, exclusions, or alternative tool hints.

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

All Context Studios MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?