Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Request a read-only Summer capability test on an authorized sample case

summer_capability_checks_test
Destructive

Request a read-only Summer capability test on an authorized sample case. Also needs investigations.request and current runtime access. Does not approve or execute customer changes.

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>",
      "capability": "<capability>",
      "expected_version": "<expected_version>",
      "case_id": "<case_id>"
    },
    "name": "summer_capability_checks_test"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idYes
companyYesSummer company ID
capabilityYes
environmentYesEnvironment that owns the resource
idempotency_keyNoReuse the same key when retrying the same change
expected_versionYesCurrent version you expect; 0 when the resource does not exist yet

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior1/5

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

The description calls the operation 'read-only', while annotations declare readOnlyHint=false and destructiveHint=true -- a direct conflict. It also supplies no behavior beyond that claim (no rate limits, no indication of what the test does to the case, no side effects), so the annotations and the text tell the agent opposite things.

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?

Three short sentences, front-loaded with the action and then scope and prerequisites. The middle sentence ('Also needs investigations.request and current runtime access') is tersely phrased and slightly ambiguous, but nothing is padded.

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?

There is no output schema, yet the description never explains what a 'capability test' returns, whether it runs synchronously, or how results are retrieved (presumably via summer_capability_checks_get). Combined with no parameter detail and an unresolved read-only vs. destructive conflict, it is not sufficient for correct invocation.

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 67%, so the schema does most of the work. The description only implies 'case_id' ('authorized sample case') and 'capability' ('capability test') and says nothing about expected_version, environment, or idempotency_key, so it adds little over the structured fields.

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 ('Request a read-only Summer capability test on an authorized sample case'), which separates it from the sibling read/list/save capability_check tools. It is clear what the tool does, though it does not explicitly contrast itself with summer_capability_checks_save or summer_capability_checks_report.

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?

'Also needs investigations.request and current runtime access' gives a prerequisite, and 'Does not approve or execute customer changes' sets a negative scope. However, no sibling is named as an alternative and no condition distinguishes requesting a test from saving or reporting one.

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