Context Studios MCP

Blog Explorer

blog_explorer

Read-only

Interactive blog browsing interface.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blog_explorer"
  }
}

Input Schema

Name	Required	Description	Default
`tag`	No	Exact or near-exact blog tag to filter published posts.
`query`	No	Search query or keyword phrase. Use the user's natural-language topic.
`language`	No	Preferred content language. Supported values are de, en, fr, and it. Some source catalogs may fall back to de or en.	en

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.0

Behavior2/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, and the description is consistent. However, the description adds no behavioral context beyond 'interactive' – no mention of pagination, result count, filtering behavior, or fallback language behavior. Since annotations already cover the read-only safety profile, the description's contribution is minimal.

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

Conciseness2/5

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

The description is a single vague phrase, which is under-specification rather than concise clarity. It fails to convey essential information in even one or two sentences, making it an ineffective use of the description field.

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?

Given the tool's moderate complexity (3 optional parameters, output schema) and the large set of sibling tools, the description is insufficient. It does not explain return values, filtering semantics, or how it differs from get_blog_posts or search_blog_knowledge. Even with the output schema available, selection remains ambiguous.

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 input schema provides detailed descriptions for all three parameters (tag, query, language) with examples and defaults. The description adds no parameter-level meaning. Per the rubric, schema coverage is 100%, so a baseline of 3 is appropriate.

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

Purpose2/5

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

The description 'Interactive blog browsing interface' indicates a blog-related tool but lacks a specific verb or resource detail. It does not distinguish from siblings like get_blog_posts or search_blog_knowledge, which likely have similar purposes. The verb 'browsing' is generic and doesn't clarify whether it filters, searches, or lists posts.

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

Usage Guidelines1/5

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

No guidance is provided on when to use this tool versus alternatives. The description is silent on use cases, prerequisites, or exclusion criteria. With many sibling tools (fetch, get_blog_posts, search_blog_knowledge), the agent has no basis for selection.

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?