Skip to main content
Glama

ArcHive

arc_session_status

State of a SessionPay session: owner, product, operator, deposit, already paid, remainder, expiry, closed.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "sessionId": "<sessionId>"
    },
    "name": "arc_session_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
sessionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden. 'State of a session' plus the field list communicates that this is a non-mutating inspection and tells the agent exactly what facets of state it will observe, which is genuinely useful given there is no output schema. It stops short of stating read-only-ness explicitly, or what happens for an unknown/expired sessionId or whether any auth is required.

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 dense sentence with zero filler, and the field enumeration is front-loaded where the agent will read it. It loses a point for being a bare fragment rather than a clause with a verb, which slightly weakens scannability.

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?

For a one-parameter read tool with no output schema, substituting a field roster for return documentation is a sensible use of the space and covers the biggest gap. Still missing are an explicit read-only statement, behavior on a missing session, and any hint of where sessionId comes from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and there is one required parameter, sessionId, which the description never mentions. The param name is largely self-explanatory, but the description adds no meaning such as the expected ID format, where to obtain it, or whether an invalid ID errors versus returning a closed/empty state.

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

Purpose3/5

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

The description names the resource (a SessionPay session) and enumerates the state it exposes, so the agent knows it is a status read. However, it is a noun fragment with no verb ('Retrieve the...'), and it never distinguishes itself from the sibling arc_sessions, leaving the read-this-one-vs-list-them choice implicit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no stated prerequisites (e.g. needing a known sessionId), and no mention of an alternative such as arc_sessions for listing. The agent must infer that this is the per-session lookup, likely from the name alone.

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.