Skip to main content
Glama

ask

Answers questions from the wiki with numbered citations using the configured provider, and optionally saves the answer back into the wiki.

Instructions

Answer a question from the wiki with numbered citations, using the provider configured in the project.

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": {
      "question": "<question>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
saveNoSave the answer back into the wiki
questionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it leaves major traits unstated: whether the call can mutate the wiki via save, whether it is expensive or slow, what it returns when the wiki has no answer, and how the "provider configured in the project" affects behavior or failure modes. Only the citation format is disclosed. The mention of a configured provider hints at an external dependency but never explains it.

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?

One front-loaded sentence with no padding; the answer format and the provider dependency are stated compactly. The provider clause is slightly cryptic but not wasteful.

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

Completeness3/5

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

For a two-parameter tool with no annotations and no output schema, the description covers what it returns at a high level (numbered citations) but omits the write-back behavior and the negative case where no supporting page exists. Adequate to invoke, not adequate to predict consequences.

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 50%: save is documented in the schema, while question has no description. The description partially compensates by establishing that question is a natural-language question answered from the wiki, but it says nothing about the save parameter or its side effect of writing the answer back into the wiki.

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?

States a specific verb and output shape: answers a question from the wiki with numbered citations. That distinguishes it from retrieval siblings like search_wiki or read_page, which return material rather than a synthesized answer. It does not name a sibling explicitly, so it stops short of a 5.

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?

The phrase "Answer a question from the wiki" implies this is the tool for question-answering rather than page retrieval, but there is no explicit when-to-use clause, no when-not, and no pointer to search_wiki or read_page as alternatives. The agent must infer the routing from the verb alone.

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