Skip to main content
Glama

See permissions and limits

access_get
Read-only

Shows what THIS connection may do for the buyer and, if it can send requests to dealerships, its own daily limit and how much of it is used today (a class or client limit may refuse sooner). It needs no extra permission and shows nothing about dealerships or prices. It also names the Ridekick account this assistant is connected to. A count of null means it could not be read. On a practice account, new requests go only to test dealerships. It answers questions about the buyer's account and limits. It is not needed before you preview or send a request.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/openWorld/destructive annotations, it discloses that no extra permission is required, that it reveals nothing about dealerships or prices, that a null count means the value could not be read, that a class or client limit may refuse before the daily limit is reached, and that a practice account routes new requests only to test dealerships — all non-obvious behavioral facts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Core facts are front-loaded, but the text sprawls across several clauses and includes a near-restatement ('It answers questions about the buyer's account and limits') that repeats the opening sentence. The parenthetical about class or client limits is compact but cryptic on first read.

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 zero-parameter, read-only introspection tool with no output schema, the description covers scope, exclusions, identity, and even a return-value edge case (null). It is close to complete; only the shape of the non-null limit/usage values is left implicit.

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 input schema has zero parameters, which is the baseline-4 case. The description correctly implies a no-argument call and adds no parameter claims that could mislead.

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 names a specific verb and resource (shows what THIS connection may do for the buyer, plus the daily send limit and its current usage) and adds the Ridekick account identity. It is clearly not the same as the request/offer siblings, though it never names a sibling tool directly.

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 states the question class it answers ('questions about the buyer's account and limits') and an explicit exclusion ('It is not needed before you preview or send a request'). No prerequisites or alternative tools are named, so a 4 rather than a 5.

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