Skip to main content
Glama

TrueInterview

Check the connection

get_account
Read-onlyIdempotent

Who this connection belongs to: the plan, this month's AI allowance, the granted scopes and whether the résumé and job search are set up. profile.next_in_chat says how to add what is missing right here in the conversation (the résumé with import_resume, the job search with update_job_search); links.setup is the website's way, the second option. Where practice is on, what is left of today's practice limits. Cheap and read-only, so call it first to check the connection works.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so 'cheap and read-only' largely restates structured data. The description does add cost context ('Cheap') and points at output fields (profile.next_in_chat, links.setup), but says nothing about permissions on 'granted scopes', rate limits, or what happens when data is missing beyond naming remediation tools.

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?

Roughly three sentences, densely packed with field names and next-step routing, with no filler. The colon-list construction ('Who this connection belongs to: ...') and the aside 'links.setup is the website's way, the second option' are slightly awkward and delay the actionable 'call it first' guidance to the end.

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?

With no output schema, the description carries the burden of explaining the return payload, and it names the major sections (plan, AI allowance, scopes, setup flags, practice limits) plus specific paths like profile.next_in_chat and links.setup. It stops short of describing value formats or what the setup flags look like, but an agent knows what it will get and what to do next.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. No misleading hints about inputs are present.

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 enumerates the concrete contents returned: 'the plan, this month's AI allowance, the granted scopes and whether the résumé and job search are set up', which is specific enough to separate it from siblings like get_my_progress or get_my_conversation. It is framed as a noun phrase ('Who this connection belongs to') rather than a verb+resource statement, so the actual action only becomes clear in the final sentence about checking that the connection works.

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?

It gives an explicit call-order rule: 'Cheap and read-only, so call it first to check the connection works.' It also routes follow-up work to named alternatives ('the résumé with import_resume, the job search with update_job_search') and presents links.setup as 'the second option'. What is missing is any statement of when not to call it, or how it relates to the overlapping progress/practice siblings.

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