Summer

Upload a new company knowledge document with original revision history

summer_knowledge_create

Destructive

Upload a new company knowledge document with original revision history. The shared library is used by all roles and environments. Existing document IDs are refused. API reference: https://api.gosummer.ai/v1/openapi.json

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>",
      "id": "<id>",
      "path": "<path>",
      "content": "<content>",
      "reason": "<reason>"
    },
    "name": "summer_knowledge_create"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Knowledge document ID
`path`	Yes
`tags`	No
`reason`	Yes
`company`	Yes	Summer company ID
`content`	Yes
`idempotency_key`	No	Reuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

B3.4/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description is not carrying the safety burden alone. It still adds real context beyond them: writes land in a library consumed by all roles and environments, and duplicate IDs are rejected rather than overwritten.

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, with the creation-only constraint front-loaded ahead of the impact note and reference link. The URL is the only marginal content, though it is a legitimate pointer to fuller docs.

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?

For a 5-required-parameter mutation with no output schema, the description adequately covers scope and the duplicate-ID rule but leaves the actual payload semantics (what 'path' must look like, how 'content' and 'reason' are used) entirely to the schema, which is only partially described.

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?

With 43% schema coverage across 7 parameters, the description needs to compensate — and it mentions none of them. The required path, content, tags, and reason fields are documented neither in the schema nor the description, leaving their format and intent unspecified.

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 and resource ('Upload a new company knowledge document') with the scope qualifier 'with original revision history'. It is clearly a creation operation, distinguishable by implication from summer_knowledge_edit, but no sibling is named explicitly.

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?

'Existing document IDs are refused' establishes a clear precondition that implicitly routes updates to summer_knowledge_edit, but the alternative is never named and no other when/when-not guidance is given.

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

All Summer tools Inspect

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.