Skip to main content
Glama

面灵AI 面试助手

list_answer_style_sources

Read-only

列出可用于「学习我的回答风格」的面试记录(用户本人回答足够多的场次),新的在前。(需要用户授权,范围 interviews:read)

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed world, so the safety profile is covered. The description adds genuinely new context beyond that: an authorization prerequisite and the required scope (interviews:read), which the agent would otherwise not know before calling.

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 compact sentences: the eligibility filter and ordering come first, the permission requirement second. No redundant restatement of the tool name and no filler.

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 read-only listing tool with a single optional parameter and no output schema, the definition covers scope, filter criteria, ordering and auth. Return-shape details and pagination behavior are the only gaps, and both are low-stakes for a limited list endpoint.

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 description coverage is 0%, so the description would need to carry the `limit` parameter, and it does not mention it at all. The schema's own default (10) and bounds (1-30) make the parameter largely self-explanatory, so the omission is minor but leaves the description adding nothing here.

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 (list interview records) plus the eligibility filter (sessions where the user answered enough) and ordering (newest first). It implicitly ties to the style-learning flow, but never names the sibling tool that consumes this list, so differentiation rests on inference.

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?

The qualifier 'usable for learning my answer style' tells the agent the situation that calls for this tool: gathering candidate sessions before style learning. It gives no explicit when-not or named alternative, but the usage context is clear.

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