Skip to main content
Glama

get_answer

Answer developer questions with cited, confidence-rated insights. Provides live symbol bodies for methods and classes directly in the answer.

Instructions

Synthesised answer with citations and a calibrated trust signal.

First call for "how does X work" / "where is Y" / "why is Z" questions.
confidence=high is content-grounded (value + citation-source + frame
gates): cite it directly, no verification Read needed. A "why" answer
whose named mechanism is absent from the retrieved source is downgraded
to medium (the rationale may be conflated). Low confidence returns
best_guesses with one-line justifications instead of an empty answer.
retrieval_quality separately rates the retrieval that fed synthesis.
When the answer names a function/method/class, ``symbol_bodies`` carries
its full live body — read that instead of a follow-up get_symbol.

Args:
    question: developer question.
    scope: optional path-prefix filter (e.g. "src/pkg/").
    repo: usually omitted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repoNo
scopeNo
questionYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Despite no annotations, the description thoroughly explains behavioral traits: confidence levels (high/medium/low), trust signal handling, retrieval_quality rating, and inclusion of symbol_bodies for live code. No contradictions with annotations.

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 key purpose and usage, but slightly verbose with detailed confidence explanations that could be more concise. Every sentence adds value, but some redundancy exists.

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?

Given the presence of an output schema, the description adequately covers return values (trust signal, confidence, retrieval_quality). It provides context on when to use versus siblings. Missing details on error handling or invalid scope but sufficient for the tool's complexity.

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?

With 0% schema description coverage, the description adds meaning for all three parameters: question as developer question, scope as optional path-prefix filter, repo as usually omitted. However, constraints like max length or format are not covered.

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 clearly states the tool produces a synthesized answer with citations and a trust signal. It distinguishes from siblings by explicitly advising to use get_symbol instead when the answer names a function/method/class.

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

Usage Guidelines5/5

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

The description specifies it is the first call for questions like 'how does X work', 'where is Y', 'why is Z'. It provides guidance on confidence levels and when to trust the answer directly versus when verification is needed.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/repowise-dev/repowise'

If you have feedback or need assistance with the MCP directory API, please join our Discord server