Skip to main content
Glama
LMPrado-DZ23

DZ23 Subagents Universal MCP

by LMPrado-DZ23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Mission status

mission_status
Read-onlyIdempotent

Check a mission's current state and recent journal events, with agent outputs shown as previews unless full outputs are requested.

Instructions

Read mission state and recent journal events. Agent outputs are returned as short previews unless include_outputs=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mission_idYesMission identifier inside the project.
project_idYesProject memory identifier. Not an authorization boundary.
events_limitNoRecent journal events to return.
include_outputsNoReturn full stored agent outputs instead of previews (can be very large).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv4.1.0
    • addedInput schema / properties / include_outputs
      Added value: +{
+  "default": false,
+  "description": "Return full stored agent outputs instead of previews (can be very large).",
+  "type": "boolean"
+}
    • changedInput schema / properties / mission_id / pattern
      Previous value: -"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,119}$"New value: +"^[a-zA-Z0-9](?:[a-zA-Z0-9._-]{0,118}[a-zA-Z0-9_-])?$"
    • changedInput schema / properties / mission_id / x-pattern-reason
      Previous value: -"must use 1-120 letters, digits, dots, underscores or hyphens and start with a letter or digit"New value: +"must use 1-120 letters, digits, dots, underscores or hyphens, start with a letter or digit and not end with a dot"
    • changedInput schema / properties / project_id / pattern
      Previous value: -"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,119}$"New value: +"^[a-zA-Z0-9](?:[a-zA-Z0-9._-]{0,118}[a-zA-Z0-9_-])?$"
    • changedInput schema / properties / project_id / x-pattern-reason
      Previous value: -"must use 1-120 letters, digits, dots, underscores or hyphens and start with a letter or digit"New value: +"must use 1-120 letters, digits, dots, underscores or hyphens, start with a letter or digit and not end with a dot"
  2. Changed12 schema fields changedv3.0.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / events_limit
      Added value: +{
+  "default": 40,
+  "description": "Recent journal events to return.",
+  "maximum": 200,
+  "minimum": 1,
+  "type": "integer"
+}
    • addedInput schema / properties / mission_id / description
      Added value: +"Mission identifier inside the project."
    • addedInput schema / properties / mission_id / maxLength
      Added value: +120
    • addedInput schema / properties / mission_id / minLength
      Added value: +1
    • addedInput schema / properties / mission_id / pattern
      Added value: +"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,119}$"
    • addedInput schema / properties / mission_id / x-pattern-reason
      Added value: +"must use 1-120 letters, digits, dots, underscores or hyphens and start with a letter or digit"
    • addedInput schema / properties / project_id / description
      Added value: +"Project memory identifier. Not an authorization boundary."
    • addedInput schema / properties / project_id / maxLength
      Added value: +120
    • addedInput schema / properties / project_id / minLength
      Added value: +1
    • addedInput schema / properties / project_id / pattern
      Added value: +"^[a-zA-Z0-9][a-zA-Z0-9._-]{0,119}$"
    • addedInput schema / properties / project_id / x-pattern-reason
      Added value: +"must use 1-120 letters, digits, dots, underscores or hyphens and start with a letter or digit"
  3. First observedv2.2.4

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover read-only, idempotency, and non-destructive nature. The description adds the preview behavior and the size caveat for include_outputs, which is marginally useful, but doesn't elaborate on response format or potential pitfalls like large responses even with previews.

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 sentences, both purposeful. The preview behavior is front-loaded, though the sentence could be clearer about the condition for previews vs full outputs.

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?

Given a read-only tool with 4 params and full schema coverage, the description is adequate but not complete. It doesn't specify default event limit or what constitutes 'recent' events, and doesn't hint at potential size issues even with previews, for example with very large journals.

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 coverage is 100%, so parameters are already well-documented. The description adds the context that include_outputs controls preview vs full, which is also in the schema. It adds no new semantic depth beyond the schema.

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?

Clearly states the tool reads mission state and journal events. However, it doesn't distinguish from the sibling 'mission_status_job', leaving ambiguity about which to use for job-specific status.

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?

Implies read-only usage and describes a key option (include_outputs), but offers no explicit guidance on when to use this versus 'mission_status_job' or when to set include_outputs to true.

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

Deploy Server

Other Tools