Skip to main content
Glama

ask_library

Ask a question about your meetings and get an answer synthesized from your local meeting library with citations, while raw transcripts stay on your computer.

Instructions

Ask a question and get an answer synthesized by LokalBot's local model from the meeting library, with meeting citations — raw transcripts never leave this computer. Needs the LokalBot app running; the first call may take up to a minute while the model loads.

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_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
questionYesThe question to answer from the user's meetings.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations present, the description carries the full behavioral burden, and it does disclose real traits: local-only processing ('raw transcripts never leave this computer'), a hard dependency on the LokalBot app, and a cold-start latency of up to a minute. However, it omits failure behavior, whether a no-answer case returns an error or an empty result, and whether answers are non-deterministic across calls — gaps that matter for a model-backed tool with zero annotation coverage.

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, front-loaded with the purpose, then privacy, then operational caveats — each clause carries distinct information with no repetition. Nothing could be cut without losing a real signal.

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 tool with no output schema, the description adequately covers what comes back (a synthesized answer with meeting citations) and the operational conditions for calling it. The remaining gap is what happens when the library has no relevant meetings or the model is unavailable, which an agent would benefit from knowing before relying on the result.

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?

There is a single required parameter at 100% schema description coverage, so the schema already explains that 'question' is the question to answer from the user's meetings. The description adds no further guidance on question phrasing, scope, or length, which is acceptable at this coverage level but not additive.

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 specific verb ('Ask a question') and a specific resource ('meeting library'), and it clarifies that the output is a synthesized answer with meeting citations rather than a document list. It does not explicitly name a sibling such as search_meetings as the alternative, so the differentiation is implied through the 'synthesized answer with citations' framing rather than stated.

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 only implied: the agent can infer this is the natural-language Q&A path versus keyword search, but the description never says when to prefer it over search_meetings or list_meetings. The one prerequisite it does give — the LokalBot app must be running — is genuinely useful operational guidance.

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