Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

List every action Summer can use for this company, the hosts each saved credential may be sent to, and the partner contacts the company named: built-in actions, connector actions and the company's own actions

summer_actions_catalog_list
Read-onlyIdempotent

List every action Summer can use for this company, the hosts each saved credential may be sent to, and the partner contacts the company named: built-in actions, connector actions and the company's own actions. Each shows its stage (off, review or automatic), whether it can ever run without a person, and its track record over 30 days: proposals, unchanged approvals, runs, uncertain runs and runs without a person. Changes nothing.

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

Input Schema

NameRequiredDescriptionDefault
companyYes
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

It significantly enhances the behavioral information provided by annotations. Beyond 'readOnlyHint: true', it adds functional constraints like 'Changes nothing,' and provides detailed behavioral metrics like 'track record over 30 days: proposals, unchanged approvals, runs, uncertain runs and runs without a person.'

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?

The information is dense, but the structure is highly efficient. The first sentence defines the scope, and the second sentence front-loads the behavioral safety and content constraints ('Changes nothing').

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

Completeness5/5

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

Given the richness of the behavioral details provided in the text (stage, track record, read-only confirmation), the tool definition is functionally complete for an agent needing to understand what this tool returns and how it operates.

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 description coverage is 0%, the description must compensate. It only uses the `company` and `environment` parameters as prerequisites for the action's visibility, but adds no semantic meaning or guidance on how those inputs affect the results or list generation.

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 purpose is exceptionally clear, specifying that it lists actions Summer can use, and explicitly defining the scope: built-in, connector, and the company's own actions. It goes beyond a simple list by detailing the metadata included (stage, track record, etc.).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

While it doesn't name a direct 'when not to use' alternative, the description defines its unique value proposition as a 'catalog' or 'discovery' tool by detailing the specific metrics returned (track record, stage). This strongly implies its use case compared to execution or management siblings.

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