Skip to main content
Glama

Brain Scanner

by io.github.kevin-lozada-santos
OverviewDiscussionsAdmin

submit_project_task

Idempotent

Update hosted submit project task using privacy-filtered project metadata.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
detailsNoOptional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content.
projectIdYesOwned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.
sessionIdNoOwned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.
executionIdNoOwned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL.
idempotencyKeyYesCaller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • addedInput schema / properties / details / description
      Added value: +"Optional bounded metadata using only the listed fields, such as summary, status and referenceIds. Not arbitrary command arguments or source content."
    • addedInput schema / properties / details / properties / status / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
    • addedInput schema / properties / executionId / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
    • addedInput schema / properties / idempotencyKey / description
      Added value: +"Caller-generated retry key. Reuse the same key and identical payload only to retry the same mutation; use a new key for a new action."
    • addedInput schema / properties / projectId / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
    • addedInput schema / properties / sessionId / description
      Added value: +"Owned project ID returned by list_linked_projects or map_project; do not use a local path or repository URL."
  2. First observed

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already declare this as a non-read-only, idempotent, non-destructive, closed-world mutation, so the safety profile is covered. The description adds one useful behavioral hint ('privacy-filtered project metadata'), but does not explain what the update actually does, what gets changed, or what is returned.

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?

A single, front-loaded sentence with no filler. However, that brevity comes at the cost of clarity, since the one clause present is ambiguous rather than informative, so it stops short of ideal structuring.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with a nested 'details' object, required idempotencyKey, and no output schema, the description is far too thin. It does not describe the effect of the update, the meaning of the privacy-filtering, or the expected response, leaving key questions unanswered despite the strong annotation coverage.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all five parameters in detail (idempotencyKey retry semantics, owned project IDs, bounded 'details' fields). The description adds only marginal context via 'privacy-filtered project metadata' and does not clarify the relationship between the 'details' sub-fields.

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

Purpose2/5

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

The description restates the tool name almost verbatim ('Update hosted submit project task'), which is close to a tautology. The only added information, 'using privacy-filtered project metadata', is vague and does not distinguish this tool from similarly-named siblings like route_agent_task, submit_node_instruction, or complete_inbox_task.

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 guidance on when to use this tool versus alternatives is provided. The description does not state prerequisites, preconditions, or which sibling tools handle related task operations, leaving the agent to infer everything from the name alone.

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

All Brain Scanner toolsInspect
Try in Browser
Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources