Skip to main content
Glama

nosebleed.si guides

Search the guides

search_guides
Read-onlyIdempotent

Search nosebleed.si for plain-English, step-by-step guides on using SI (AI) for an everyday or small-business task, for example "explain a letter", "plan a trip", "write a quote", "VAT", "take a screenshot". Returns the best matches with links.

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": {
      "query": "<query>"
    },
    "name": "search_guides"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many results (default 5).
queryYesWhat the person wants to do, in a few words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/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, closed-world), so the bar is lower. The description adds genuinely useful context beyond them: the source domain, the nature of the corpus, and the return shape ('best matches with links'), which matters since there is no output schema.

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?

Two sentences, front-loaded with the domain and purpose, then the return behavior. The run of example queries is long but each one earns its place by anchoring the intended query style, so there is no real filler.

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 two-parameter read-only search with full schema documentation, the definition covers source, intent, expected query style, and return format. With no output schema, the brief note that results include links is enough; only sibling differentiation 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%, so the schema already defines both parameters, including the query being 'what the person wants to do, in a few words' and limit defaulting to 5. The example phrases give a feel for query granularity but add little semantic detail the schema does not already carry.

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

Purpose4/5

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

The description names a concrete verb (search) and a concrete resource (plain-English step-by-step guides on nosebleed.si), and the example queries make the content type tangible. It does not, however, distinguish itself from the siblings list_guides or get_guide, so an agent must infer which of the three to pick.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the examples ('explain a letter', 'VAT', 'take a screenshot') show the kind of task that should be routed here. There is no explicit when-to-use or when-not-to-use guidance relative to list_guides or get_guide, leaving the routing decision to inference.

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.

Resources