PersonIQ

Account balance and scopes

get_account

Read-only

Your current credit balance and the capabilities this credential holds. Free.

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

Name	Required	Description	Default
`format`	No	Rendering of the human-readable text channel. "prose" (default) is a compact summary an agent can reason over; "json" repeats the data verbatim; "report" is a formatted Markdown report to show a person; "html" is a standalone HTML document for saving, printing or PDF. Machine-readable structuredContent is always included either way.

Output Schema

Name	Required	Description	Default
`data`	Yes
`apiVersion`	Yes
`disclaimer`	Yes
`balanceNotice`	No
`suggestedNext`	No
`criminalCaveat`	No
`notConsumerReport`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 3, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's one genuine addition is the cost disclosure ("Free"), which is not in the annotations and matters for call budgeting, but nothing is said about freshness, caching, or what happens if the credential is invalid.

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?

Two short sentences with zero redundancy, and the substantive content (balance plus scopes) is front-loaded. The clipped "Free." fragment is efficient rather than confusing, though the overall text is so sparse that it borders on under-specification for the usage dimension.

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 an output schema present, return values need no explanation, annotations cover the safety profile, and the single parameter is fully documented in the schema. The description supplies the essential framing (what data comes back and that it costs nothing), leaving only minor gaps such as guidance on when to call it.

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?

There is a single optional parameter whose schema description is exhaustive (100% coverage), including a full explanation of each enum value and the note that structuredContent is always returned. The description adds nothing about the format parameter, so the baseline 3 applies.

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 the resource (this credential/account) and the two things returned: current credit balance and the capabilities the credential holds. That is specific enough for an agent to know exactly what it gets, and no sibling tool in the list overlaps with account/balance retrieval, so explicit differentiation is unnecessary.

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 explicit when-to-use or when-not-to-use guidance, and no alternatives are mentioned. The only contextual nudge is the word "Free," which hints it is a cheap call to make, but an agent must infer on its own that this is the tool to check balance or verify scopes before attempting other operations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PersonIQ tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?