Skip to main content
Glama

rental-review

Recognize this account

recognize_account
Read-onlyIdempotent

Say which TrueRent account this sign-in is linked to. Returns the company name and account number. Does not read equipment, prices, invoices, or orders. Does not send anything. Requires a TrueRent sign-in issued for this plugin.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
messageYes
signed_inYes
recognizedYes
company_nameYes
account_numberYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower; the description still adds real value by disclosing the return payload and the prerequisite that the sign-in must be one issued for this plugin. It also explicitly states nothing is sent, reinforcing the no-side-effect profile. It does not describe what happens when the sign-in is not recognized, which is the main remaining gap.

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?

Four short sentences, front-loaded with the purpose and the return value before the exclusions. The two "Does not..." sentences are slightly enumerative, but each removes a plausible misread, so the wording mostly earns its place.

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 zero-parameter, read-only lookup with an output schema, the description covers purpose, return shape, authentication prerequisite, and scope limits. Nothing an agent needs in order to call it correctly 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?

The tool takes no parameters and the schema is fully described, so there is no parameter meaning to add. The description correctly avoids inventing inputs and instead frames the implicit input as the current sign-in context.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Say which TrueRent account this sign-in is linked to" names a specific verb and resource, and the follow-up sentence states exactly what comes back (company name and account number). The negative clauses carve out clear boundaries against the sibling tools that deal with equipment, prices, invoices, and orders.

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 description makes the triggering situation clear (an agent holding a sign-in that needs to be resolved to an account) and rules out adjacent jobs by listing what it does not read. It stops short of naming a concrete alternative tool to use instead for those excluded tasks, so routing relies on the sibling names rather than explicit direction.

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