Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Prepare editable operator guidance from an exact active workflow revision and feedback

summer_workflows_request_text
Read-onlyIdempotent

Prepare editable operator guidance from an exact active workflow revision and feedback. Starts no investigation and executes no 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": {
      "company": "<company>",
      "environment": "<environment>",
      "id": "<id>",
      "expected_revision": "<expected_revision>"
    },
    "name": "summer_workflows_request_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
companyYes
feedbackNo
environmentYes
expected_revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

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, idempotentHint=true, destructiveHint=false, and openWorldHint=true. The description adds a useful boundary that no investigation is started and no action is executed, but it does not describe return format, authorization, or rate-limit behavior.

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 tightly written sentences with zero filler. The primary purpose is front-loaded, and the second sentence efficiently adds a key behavioral boundary.

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?

With five parameters, 0% schema description coverage, and no output schema, the description is too thin to call the tool confidently. It does not explain the workflow id, company scope, environment choice, revision precondition, or what the generated text looks like.

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%, so the description must carry parameter meaning. It references 'feedback' and 'exact active workflow revision' indirectly, but leaves the required parameters 'company', 'environment', and 'id' unexplained, and does not clarify expected_revision semantics.

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?

States a specific verb ('Prepare') and resource ('editable operator guidance'), plus the source inputs ('exact active workflow revision and feedback'). It is clear what the tool does, though it does not explicitly differentiate itself from sibling workflow tools such as history/list/save.

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?

The boundary 'Starts no investigation and executes no action' implies this is not an investigation or execution tool, which helps frame usage. However, it does not explicitly say when to use this versus sibling workflow tools or name any alternatives.

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

All Summer toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources