Skip to main content
Glama

Interview fact-checks done so far

get_interview_checks
Read-only

List of interviews already checked on Orb Studio, or one full card by YouTube video id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_interview_checks"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoYouTube video id

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that results represent already-checked interviews and that a single id yields a 'full card', which hints at the return shape. It does not say what a card contains, how the list is ordered, or whether pagination or limits apply.

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?

A single compact sentence with the collection case front-loaded and the single-item case after it. Nothing is redundant, though the telegraphic 'List of interviews' phrasing is slightly clipped.

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?

This is a simple, single-parameter read tool, so modest coverage is reasonable. However, with no output schema, the description never characterizes what 'already checked' or a 'full card' actually contains, leaving an agent unsure what data comes back.

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% and the schema already defines the id as a YouTube video id, so the baseline is 3. The description earns an extra point by explaining the behavioral effect of the parameter: supplying it switches from a collection listing to a single full card, which the schema does not convey.

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 concrete verb-and-resource pair: it lists interviews previously fact-checked on Orb Studio, and can return a single full card when given a YouTube video id. The two retrieval modes are clear. It does not explicitly distinguish itself from the sibling check_interview, so the reader must infer that this one reads existing results while the sibling runs a check.

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 description implies the usage pattern: omit the id to get a list, supply the id to get one card. That conditional is useful but only implied, and there is no explicit statement of when to prefer this over check_interview or any other sibling.

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.