Skip to main content
Glama

nosebleed.si guides

Read a guide

get_guide
Read-onlyIdempotent

Get the full text of one nosebleed.si guide: steps, copyable example prompts, follow-up questions and warnings. Pass the page address from search_guides or list_guides.

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": {
      "url": "<url>"
    },
    "name": "get_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe guide address, e.g. https://nosebleed.si/business/write-a-quote-that-wins-the-job/ or /basics/take-a-screenshot/

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds value beyond that by telling the agent what the payload actually contains — full page text with prompts, follow-ups, and warnings — which matters since there is no output schema. It does not say how failures (bad or missing URL) are surfaced.

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 sentences, both earning their place: the first defines the resource and its contents, the second states the parameter's source. The most decision-relevant information (what you get, where the input comes from) is front-loaded with no padding.

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 one-parameter read tool with full schema coverage and complete annotations, the description covers purpose, input provenance, and return contents — everything needed to call it correctly. Only minor gaps remain, such as behavior on an invalid or stale URL.

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% and the url parameter already carries two worked examples, so the structured field does most of the work. The description still adds meaningful semantics by stating the URL's provenance ('from search_guides or list_guides'), making clear it is a page address rather than an arbitrary identifier.

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 names a specific verb and resource ('Get the full text of one nosebleed.si guide') and scopes it to a single guide, then enumerates what the text contains (steps, copyable example prompts, follow-up questions, warnings). An agent can immediately distinguish this retrieval tool from search_guides and list_guides.

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 explicit context for invocation: pass a page address obtained from search_guides or list_guides, which establishes the search/list-then-fetch workflow. It stops short of stating when not to use it (e.g., when only titles are needed, use list_guides), so it falls just short of full routing guidance.

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