Skip to main content
Glama

ai_modeling_uv_context

Read-only

Inspect UV candidates, active tasks, and the next permitted action for a project and current operator.

Instructions

Inspect UV candidates, active tasks and the next permitted action.

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": {
      "project_id": "<project_id>",
      "current_operator_id": "<current_operator_id>"
    },
    "name": "ai_modeling_uv_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
current_operator_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds almost nothing beyond that: the phrase "next permitted action" implies a state machine and gating logic, but it never explains what determines permission, whether the result reflects live server state, or how the three listed facets relate. With annotations doing the safety work, this remains thin rather than contradictory.

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 or repetition. It is efficient, but the brevity leans toward under-specification rather than genuine economy.

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?

No output schema exists and no parameters are documented, so the description carries the full burden of explaining both inputs and response shape — and it does neither. For a tool that appears to report workflow state and permitted transitions, the definition is far too thin to call correctly with confidence.

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

Parameters1/5

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

Both parameters (`project_id` and `current_operator_id`) are required yet have 0% schema description coverage, and the description mentions neither. The reader cannot tell whether `current_operator_id` scopes the response to one operator's permissions or merely identifies the caller, which materially changes the meaning of "next permitted action".

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 gives a verb ("inspect") and a three-part scope (UV candidates, active tasks, next permitted action), so the general domain is discernible. However, "UV" is never expanded and the scope overlaps heavily with the sibling `ai_modeling_uv_inspect`, leaving an agent unable to tell which of the two to pick. It is vague rather than tautological.

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 statement of when to call this versus `ai_modeling_uv_inspect`, `ai_modeling_uv_preview`, `ai_modeling_uv_apply`, or any other workflow sibling. No prerequisites, no sequencing, no exclusions. An agent must guess the workflow position of this tool.

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