Skip to main content
Glama
This connector has been deprecated

This was a duplicate manual listing. Use Summer’s official listing, imported from the official MCP Registry. Summer’s MCP server remains active at https://api.gosummer.ai/mcp. Setup and documentation: https://gosummer.ai/docs/mcp-clients.

Read current and latest shared publication versions, adoption history and the company's business profile

summer_knowledge_adoptions
Read-onlyIdempotent

Read current and latest shared publication versions, adoption history and the company's business profile.

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>"
    },
    "name": "summer_knowledge_adoptions"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

The description confirms the read-only nature of the operation, which is already explicitly defined by the 'readOnlyHint: true' annotation. It adds no new behavioral constraints or risk disclosure beyond what is already structured.

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?

The definition is maximally concise, combining all necessary functional elements (action, resources, and data points) into a single, fluid sentence without any filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It is highly complete regarding the *content* retrieved, successfully covering all data types mentioned in the title. However, without an output schema, full completeness cannot be achieved.

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?

Since schema coverage is 0%, the description should define the parameter's role. While it implies the 'company' parameter is necessary to get the 'company's business profile,' it adds no specific guidance or constraints beyond the schema's type and format.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Read') and specifies the three distinct resources being retrieved: publication versions, adoption history, and the company's business profile. This is highly specific.

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 description is descriptive of content but offers no guidance on operational usage, such as when this is preferred over a related sibling tool. Usage is left up to the agent's internal context.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources