Skip to main content
Glama

Kariaa Agents

My submissions

my_submissions
Read-only

Use when the person asks how their DataHouse tasks stand. Every DataHouse task the person joined, newest first, with its stage (pending_review, sample_needed, in_review, approved, rejected).

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

Input Schema

NameRequiredDescriptionDefault
limitNo

Output Schema

NameRequiredDescriptionDefault
submissionsNoEach task joined, with stage and samples

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered; the description adds real value on top by stating ordering (newest first) and enumerating the possible stage values the agent will see. The remaining gap is pagination and default page size, which matter for a list tool but are not disclosed.

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 sentences, front-loaded with the triggering user intent, then the result shape. There is no filler and nothing is buried.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile; the description covers trigger, scope, ordering, and status semantics. What is missing is how the optional limit behaves and whether results are paginated - the one thing an agent must guess when calling it.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description is the only place the 'limit' parameter could be explained, and it says nothing about it - not its meaning, default value, or the maximum of 50. The schema's type and range constraints make the bare mechanics inferable, but the description fails to compensate for the coverage gap as the rubric requires at low coverage.

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 uses a clear noun resource ('Every DataHouse task the person joined') and specifies scope plus ordering, so an agent can distinguish this personal-history listing from single-item siblings like get_submission or job-browsing siblings like list_tasks. It stops short of explicitly naming any sibling to contrast with, keeping it at 4 rather than 5.

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?

'Use when the person asks how their DataHouse tasks stand' is an explicit, concrete trigger tied to a user intent, which is exactly what an agent needs at routing time. It gives no exclusions or named alternatives, so nothing tells the agent when not to pick this tool.

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.