Skip to main content
Glama

Read a profile, post or guide

fetch
Read-onlyIdempotent

Read one Knowasiak profile, post or help guide in full, as Markdown, by the id from search (e.g. "profile:AdityaGaurav", "post:36405" or "help:discover-people"), or by its knowasiak.com address. A profile includes its links and recent posts; a post its replies.

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": {
      "id": "<id>"
    },
    "name": "fetch"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAn id from search: "profile:<username>", "post:<number>", "help:<slug>" or "page:<slug>"; or a knowasiak.com URL.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / id / description
      Previous value: -"An id from search: \"profile:<username>\" or \"post:<number>\"."New value: +"An id from search: \"profile:<username>\", \"post:<number>\", \"help:<slug>\" or \"page:<slug>\"; or a knowasiak.com URL."
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare this as a safe, idempotent, open-world read, so the description's job is to add behavioral detail — and it does: output is full-content Markdown, and a profile response expands to include its links and recent posts while a post includes its replies. What is missing is failure behavior for an unknown or malformed id.

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 verb and resource are front-loaded in the first clause, and the second sentence efficiently conveys payload composition. The parenthetical example list is slightly dense but earns its place by showing exact id syntax.

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?

For a one-parameter read with no output schema, the description covers input forms, response format, and what each resource type returns, which is enough for an agent to call it correctly. The only loose end is the omitted 'page' id type, a minor omission rather than a blocking gap.

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 single id parameter is already fully documented and the baseline is 3. The description adds concrete example values, but it also lists only profile/post/help forms while the schema additionally accepts 'page:<slug>', leaving a small mismatch that does not fully compensate.

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?

Names a specific verb (read) and the exact resources (one profile, post or help guide), states the output format (Markdown), and gives concrete id forms. An agent can distinguish this single-item read from the list-oriented siblings like search and latest_posts without opening the schema.

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?

The phrase 'by the id from search' implicitly routes the agent through search first, which is useful sequencing guidance, and the accepted input forms are spelled out. It stops short of explicit exclusions or naming a sibling alternative (e.g. when to use person_details instead), so it is clear context rather than full when/when-not 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