Skip to main content
Glama

DECA Labs

Your tests

list_my_tests
Read-only

Every test paid with this API key's workspace, newest first. Needs a key.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that: the result set is scoped to the API key's workspace only, ordering is newest-first, and a key is required. It says nothing about result limits or pagination, which keeps it at a solid 3 rather than higher.

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, front-loaded with scope and ordering, with no filler. The phrasing 'paid with this API key's workspace' is slightly awkward and could read as 'belonging to this API key's workspace', a minor clarity tax but not wasted space.

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 zero-parameter read-only listing with no output schema, the essentials are present: scope, ordering, auth requirement. However, since no output schema exists, the description could reasonably state what a test entry looks like or whether results are capped/paginated — an agent cannot tell if 'every test' means all results or a limited first page.

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 schema carries no semantics to supplement and the baseline is 4. The description appropriately adds no parameter discussion and instead spends its words on scope and ordering.

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 (tests) and its scope (every test paid with this API key's workspace), which clearly separates a bulk listing from the singular get_test sibling. It never uses an explicit verb like 'list', relying on 'Every test ... newest first' to imply enumeration, so it is clear but not maximally crisp.

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 statement and no named alternative — nothing tells the agent to call get_test for a single test or get_my_ideas for a different resource. The only guidance is an implicit 'this returns everything in your workspace' framing, leaving selection between siblings to inference.

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.

Resources