Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Open the Summer workspace for a human to choose a queued message and click Send now outside sending hours

summer_messages_queued_send_now
Read-onlyIdempotent

Open the Summer workspace for a human to choose a queued message and click Send now outside sending hours. Returns a UI handoff only; API, CLI and MCP callers cannot override hours or send a message. The signed-in person must have current sending access. Consent, ordering, exact approvals and original receipt checks remain enforced.

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_messages_queued_send_now"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses that the return is a UI handoff only, that programmatic callers cannot override sending hours, that the signed-in person needs current sending access, and that consent/ordering/approval/receipt checks still apply. These are substantive operational constraints an agent could not infer from the annotations.

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?

Purpose is front-loaded in the first clause, followed by scoping and enforcement caveats in descending order of importance. The final sentence listing 'consent, ordering, exact approvals and original receipt checks' is slightly vague filler but does convey that downstream validation persists.

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?

The behavioral picture is thorough and no output schema is needed since the description says it returns a UI handoff. However, with two required parameters at 0% schema coverage and no description of them, an agent cannot confidently construct a valid call from this definition alone.

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, and it does not — neither the company UUID nor the staging/production enum is mentioned or explained. The only hints ('workspace', 'signed-in person') do not map clearly to either required parameter.

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?

States a specific action (open the Summer workspace for a human to pick a queued message and click Send now) and, critically, clarifies that this is a UI handoff rather than an actual send. An agent can distinguish it from the sibling summer_messages_queued_list (which lists messages) without opening either schema.

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?

The 'outside sending hours' qualifier establishes the condition for use, and 'API, CLI and MCP callers cannot override hours or send a message' makes the negative case explicit. It stops short of naming a concrete alternative path or the list-then-handoff sequence, so not a 5.

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