Skip to main content
Glama
Sign In
spoofzy

spoofzy

by spoofzy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Spoofzy account and limits

spoofzy_account
Read-onlyIdempotent

Checks connection, configured keys, plan, available tools and costs, file limits, prepaid units, and result locations; call before processing or when a run is refused. Free and read-only.

Instructions

Check the Spoofzy connection: which keys are configured, the plan, which tools are available (Spoofer, many versions, Studio looks, Metadata Cleaner, workflows), what they cost, file limits, prepaid units and where results are saved. Call it first in a conversation and whenever a run is refused. Free and 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": "spoofzy_account"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered. The description adds genuinely new context — that the call is free, that it reports remaining limits and prepaid units, and that it fails usefully when a run is refused — which is exactly the diagnostic behavior an agent needs. It does not describe the response shape in detail, but with no output schema the enumeration of contents covers the essentials.

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?

The verb and scope are front-loaded, followed by the trigger conditions, so an agent gets the actionable part immediately. The long parenthetical catalog of tool families is the densest part, but each item informs the agent what account facts are retrievable, so little of it is wasted.

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?

With zero parameters and no output schema, the description carries the full burden of explaining what comes back, and it does so by listing every category of returned information. Combined with the explicit 'call it first' and 'call it when refused' guidance, an agent has everything needed to invoke it correctly.

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 the baseline of 4 applies; there are no arguments whose meaning the description could clarify or obscure. The description correctly implies a parameterless, ambient-state lookup rather than suggesting any input is needed.

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?

The description states a specific verb and resource ('Check the Spoofzy connection') and then enumerates exactly what that check surfaces: configured keys, plan, available tools, costs, file limits, prepaid units, and output locations. That enumeration clearly separates it from siblings like spoofzy_list_runs or spoofzy_spoof, which act on individual artifacts rather than account state.

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 gives two concrete invocation triggers: 'Call it first in a conversation' and 'whenever a run is refused.' That is strong routing guidance for both the proactive and error-recovery cases. It stops short of a when-not-to-use statement or naming a sibling as the alternative, so it lands just under the top mark.

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

Deploy Server

Other Tools