Skip to main content
Glama

Kariaa Agents

Get a submission

get_submission
Read-only

Use when the person asks about one DataHouse task. One task the person joined: stage, staged files, review outcome and the next step.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "submission_id": "<submission_id>"
    },
    "name": "get_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
submission_idYes

Output Schema

NameRequiredDescriptionDefault
nextNoWhat to do next
stageNoWhere it stands
submission_idNoThe application

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description adds only a summary of returned content, which is largely duplicated by the output schema. It says nothing about lookup failure behavior when a submission_id is unknown or inaccessible.

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

Conciseness3/5

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

Two sentences with no filler, and the usage trigger is front-loaded. The second sentence is a comma-spliced fragment list that reads awkwardly and spends words restating return fields the output schema already provides.

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?

With an output schema present, return values do not need explaining, and the safety annotations are complete. What remains missing is disambiguation from get_task and my_submissions and any mention of what the submission_id refers to, which for a retrieval tool in a crowded sibling set is a real gap.

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?

Schema coverage is 0% and the single parameter is undocumented beyond type/format, but this is a one-parameter lookup where the name submission_id and uuid format are self-explanatory. The description does not add meaning beyond the schema name, so a 4 rather than 5 is warranted, but the low parameter count keeps the practical gap small.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies a single-record lookup and enumerates the returned fields (stage, staged files, review outcome, next step), which makes the resource concrete. However, it calls the entity a 'DataHouse task' rather than a submission, which blurs the line against the sibling get_task and makes it harder to tell which tool an agent should open. The verb is only implied by the name.

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?

'Use when the person asks about one DataHouse task' supplies a trigger condition, and the emphasis on 'one' implicitly contrasts with a list tool such as my_submissions. There is no explicit when-not guidance and no sibling is named as an alternative, so an agent must infer the boundary with get_task and my_submissions.

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.