Skip to main content
Glama

Search curated guidance

search_guidance
Read-onlyIdempotent

List curated guidance records that match a target coding agent, model family, scope and topic. Returns official model guidance, platform documentation and Agent Skills standard records with labels, applicability and the date each source was verified. PromptingCraft.com methodology records are returned only when kind is promptingcraft_methodology and are never official provider guidance. Inputs are fixed categories only. Use get_guidance for the full record.

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

Input Schema

NameRequiredDescriptionDefault
kindNoRecord kind. Omit for official guidance, platform documentation and standards.
limitNoMaximum number of results (1-20).
scopeNogeneral: broad provider technique; model_specific: applies only to a named model or interface.any
topicNoGuidance topic.
model_familyNoModel family the target agent will run, if known. Use other for a family without curated guidance.any
target_agentNoCoding agent the prompt is for.any

Output Schema

NameRequiredDescriptionDefault
notesYes
filtersYes
resultsYes
returnedYes
provenanceYes
total_matchesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / model_family / enum
      Previous value: -[
      -  "openai",
      -  "anthropic",
      -  "other",
      -  "any"
      -]New value: +[
      +  "openai",
      +  "anthropic",
      +  "deepseek",
      +  "kimi",
      +  "other",
      +  "any"
      +]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

The annotations already establish read-only, idempotent, non-destructive, closed-world behavior. The description adds useful behavioral context about returned labels, applicability, verification dates, and the special exclusion of methodology records from official guidance.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and stays reasonably tight. A few sentences carry schema-adjacent detail, but each sentence contributes routing or behavioral information.

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?

With an output schema present and annotations covering safety, the description is close to complete for an agent to call this tool correctly. Its main omission is not distinguishing itself from check_source_freshness, which is another listed sibling.

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 coverage is 100%, so the schema already carries the detailed parameter documentation. The description still adds meaning by clarifying that inputs are fixed categories only and that methodology records are returned only when kind is explicitly set to promptingcraft_methodology.

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?

The description states a specific verb and resource: list curated guidance records, with the matching dimensions named explicitly. It also distinguishes the tool from get_guidance by saying that tool is for the full record.

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?

It gives clear routing guidance for get_guidance and explains that PromptingCraft methodology records require kind=promptingcraft_methodology. It does not mention when to use check_source_freshness instead, so it stops short of full sibling coverage.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.