Examova — Exam Prep

Search Study Guides

search_guides

Read-onlyIdempotent

Search Examova's free public study guides and exam-tip articles (blog). Returns titles, summaries and links; use get_guide to read one in full.

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": "search_guides"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Max results (default 6)
`query`	No	Optional keyword, certification or module, e.g. "L4M5", "PMP", "negotiation"

Output Schema

Name	Required	Description	Default
`guides`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 25, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower; the description adds that the corpus is free public content and that results are titles/summaries/links, which tells the agent results are shallow and require a follow-up call. It doesn't mention result caps or empty-result behavior beyond the schema's limit maximum.

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 clauses, front-loaded with the resource and scope, followed by the return shape and the follow-up route. No wasted wording.

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

Completeness5/5

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

An output schema exists, so return values needn't be spelled out further, and the description still notes the shallow result shape. For a 2-parameter read-only search with full schema coverage and a named next-step sibling, nothing an agent needs is missing.

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% and both parameters are documented with examples and bounds, so baseline 3 applies. The description adds no parameter meaning beyond the schema.

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?

Specific verb (search) plus a clearly scoped resource (free public study guides and exam-tip blog articles), and it names what the results contain. It also distinguishes itself from get_guide, the sibling that reads a full guide.

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

Usage Guidelines4/5

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

Explicitly tells the agent to use get_guide to read a guide in full, which sets the boundary between discovery and retrieval. It doesn't differentiate from the other search tools (search_site, search_practice_questions), so not a full 5.

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

All Examova — Exam Prep 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?