Skip to main content
Glama

get_my_appealable_penalties

List your own credit penalties still eligible for appeal. Always free.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A3.5/5.0
Behavior2/5

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

With no annotations, the description carries full burden for behavioral disclosure. It only mentions that the tool is 'Always free,' but fails to describe other important behaviors such as data freshness, idempotency, or whether it requires authentication.

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 short sentences, no filler, and the most important information is front-loaded. Every word earns its place.

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 tool with no parameters and no output schema, the description is minimal. It lacks guidance on what the output looks like and when to use it, but it does convey the essential purpose. It is adequate but leaves gaps for more complex decision-making.

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?

There are no parameters, so the baseline is 4. The description adds value by clarifying the scope ('your own' and 'still eligible for appeal'), which the empty schema does not convey.

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 clearly states the action ('List') and the specific resource ('your own credit penalties still eligible for appeal'). It distinguishes itself from sibling tools like submit_appeal by focusing on listing appealable penalties.

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?

No explicit guidance on when to use this tool versus alternatives. The phrase 'Always free' hints at no cost but does not provide context for when to use it, nor does it mention any prerequisites or when not to use it.

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.

TDQS

B3.3/5.0
Disambiguation5/5

Each tool targets a distinct action or resource. For example, compose_prompt assembles prompts, search_blocks searches, register_agent initiates registration. Even related tools like get_block and get_block_versions are clearly differentiated by purpose (current vs history).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern in snake_case (e.g., compose_prompt, submit_block, verify_registration). No mixing of naming conventions, making it predictable for an agent.

Tool Count4/5

With 20 tools, the scope is broad but well-justified by the diverse functionality (search, submission, ratings, registration, DMCA, etc.). It is on the higher end but not excessive for a full-featured platform.

Completeness3/5

The tool set covers core workflows like searching, viewing, creating, and rating blocks, but lacks update or delete operations for blocks. Also missing tools for managing user profiles or block editing, which are notable gaps.

Resources