Skip to main content
Glama
Sign In
CARBON Studio Pro

CARBON Studio Pro

by jarbon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

studio_steer

Persist user guidance and priority on a finding so the agent reads it before selecting the next check.

Instructions

Persist user guidance on a finding. The agent reads it before selecting the next check.

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": {
      "runId": "<runId>",
      "findingId": "<findingId>",
      "note": "<note>",
      "priority": "<priority>"
    },
    "name": "studio_steer"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteYes
runIdYes
priorityYes
findingIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already establish that this is a non-read-only, non-destructive, closed-world write. The description adds that the persisted guidance is later read by the agent before choosing the next check, which is useful behavioral context beyond the annotations, but it does not cover permissions, durability, or side effects.

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 short sentences, both front-loaded and free of filler. The purpose is stated first, followed immediately by the key behavioral consequence.

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 tool with four required parameters, no schema descriptions, and no output schema, the description is too sparse. It communicates the core purpose but omits parameter meaning, priority semantics, and invocation context needed to call it correctly.

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%, and all four parameters are required, so the description carries the burden of explaining them. It only vaguely hints that the guidance concerns a finding, leaving runId, priority, note limits, and the relationship between parameters unexplained.

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 states a specific verb and resource: 'Persist user guidance on a finding.' It distinguishes the tool from generic update/save siblings by describing the artifact persisted and its role, but it does not explicitly name an alternative tool or scope boundaries.

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?

The description explains that the agent reads the guidance before selecting the next check, which is behavioral context rather than invocation guidance. It gives no explicit when-to-use, when-not-to-use, or alternative sibling comparison, leaving the agent to infer the trigger from the purpose alone.

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