Skip to main content
Glama
X Use

X Use

by felixlark

Check X authentication and credits

x_status
Read-onlyIdempotent

Verify xurl version and safe auth metadata, check OAuth2 user access, and read developer credit balance without exposing tokens or writing to X.

Instructions

Check xurl version and safe auth metadata, verify OAuth2 user access, and read the developer credit balance. Does not print tokens or write to X. Read-only.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description still adds real value beyond them by disclosing that it surfaces the OAuth2 auth requirement and that tokens are never printed, which matters for an agent reasoning about credential exposure.

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

Conciseness5/5

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

Two tight sentences, front-loaded with what is checked, followed by explicit non-behaviors. Nothing is padded and no sentence is wasted.

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 parameterless diagnostic with rich annotations and no output schema, the description adequately conveys scope and return content (version, auth metadata, credit balance). It stops short of telling the agent what a negative result looks like, e.g. how an unauthenticated or exhausted-credit state is reported.

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 applies. The description correctly does not invent inputs.

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?

Names three concrete checks: xurl version, OAuth2 user access, and developer credit balance. That specificity makes it unmistakable against content-oriented siblings like x_post or x_search, which an agent could never confuse with a diagnostic call.

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

Usage Guidelines3/5

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

Usage is only implied — an agent can infer this is the pre-flight auth/credit check, but the description never says 'call this before posting' or 'use when a post fails with auth errors'. No exclusions or alternatives are stated.

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