Skip to main content
Glama

BlockRazor Docs

by io.blockrazor

askQuestion

Read-only

Ask a natural-language question about BlockRazor and get a synthesized answer, with links to the source pages. Prefer this over searchDocumentation when you want a direct answer to a question rather than a list of matching pages; use searchDocumentation/getPage when you need to browse or read full pages yourself.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
goalNoThe broader end goal you are ultimately trying to accomplish (as/on behalf of the user). Used to tailor the answer to be most useful for your goal. Optional.
questionYesThe natural-language question to answer about BlockRazor.

TDQS

A4.4/5.0
Behavior3/5

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

Annotations already cover read-only and open-world hints. Description adds that answers are synthesized with source links and can be tailored via 'goal' parameter, but doesn't detail other behavioral traits like latency or error handling.

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?

Two efficient sentences: first states core functionality, second gives usage guidance. No unnecessary words, well front-loaded.

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

Completeness4/5

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

For a tool with two parameters and no output schema, the description adequately explains the return format (synthesized answer with links) and the role of the optional 'goal' parameter. Missing details on edge cases but still complete for typical use.

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

Parameters4/5

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

Schema already describes both parameters well (100% coverage). Description adds context that 'goal' tailors the answer, which goes beyond the schema description.

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?

Clear verb ('ask'), resource ('BlockRazor'), and outcome ('synthesized answer with links'). Explicitly distinguishes from sibling 'searchDocumentation'.

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?

States when to prefer this tool (direct answers) versus alternatives ('searchDocumentation'/'getPage' for browsing). Provides clear guidance on usage context.

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

All BlockRazor Docs 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.4/5.0
Disambiguation5/5

Each tool has a clearly distinct purpose: askQuestion provides synthesized answers, getPage fetches full page content, searchDocumentation returns search results, and sendFeedback reports issues. There is no overlap in functionality.

Naming Consistency5/5

All tool names follow a consistent camelCase verb_noun pattern (e.g., askQuestion, getPage, searchDocumentation, sendFeedback), ensuring predictability.

Tool Count5/5

With 4 tools covering documentation browsing, search, Q&A, and feedback, the count is well-scoped for the server's purpose without being too few or too many.

Completeness5/5

The tool set covers all necessary operations for a documentation server: retrieving pages, searching, asking questions, and reporting issues. There are no obvious gaps.

Resources