Skip to main content
Glama

AceRound AI Interview Copilot

get_official_knowledge_base

Read-only

Read an official knowledge base: description and an overview of its entries (one per line); pass indexes for the full entries with sources. The ID comes from list_official_knowledge_bases. (Requires the user's sign-in with scope interviews:read.)

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": "get_official_knowledge_base"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesOfficial knowledge base ID
indexesNoEntry numbers to read in full (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish readOnly, non-destructive, closed-world, so the description doesn't need to repeat safety. It adds genuinely new behavioral context: an auth requirement with a specific scope ('interviews:read') and the shape of the response (overview lines vs. full entries with sources). Rate limits and size caps are left to the schema.

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 dense sentences plus a parenthetical auth note; the resource and its return shape are front-loaded, and the fallback pointer to the list tool and the scope requirement follow in priority order. No sentence is filler.

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 two-parameter read tool with full schema coverage and read-only annotations, the description covers what an agent needs: where the ID comes from, what the default response looks like, how to get full entries, and the auth scope. No output schema exists, and the return shape is described in prose, so nothing material is missing.

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%, so the baseline is 3, but the description adds real meaning: it explains the default overview behavior and that indexes upgrade specific entries to full text with sources, which clarifies the intent of an otherwise ambiguous integer array. That is value beyond the schema's 'Entry numbers to read in full (1-based)'.

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 resource ('Read an official knowledge base') and describes exactly what comes back: a description plus a one-entry-per-line overview, with full entries when indexes are supplied. The word 'official' plus the pointer to list_official_knowledge_bases separates it from the generic get_knowledge_base sibling, though the difference between the two is never spelled out.

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?

Gives a concrete precondition and routing hint: 'The ID comes from list_official_knowledge_bases,' which tells the agent where to get the required argument. It also implies the two-step flow (overview first, then pass indexes for detail). It does not state when to prefer this over get_knowledge_base or other KB readers.

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