Skip to main content
Glama
Sign In

Summer

by ai.gosummer.api
OverviewDiscussionsAdmin
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.

Save the demo pharmacy-call voice service, voice and vocabulary with the expected revision

summer_pharmacy_calls_settings_update
Destructive

Save the demo pharmacy-call voice service, voice and vocabulary with the expected revision. provider is openai_live (OpenAI GPT-Live, default) or elevenlabs; omitted provider or openai_voice keeps the saved value. Starts no call.

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>",
      "revision": "<revision>",
      "voice_id": "<voice_id>",
      "vocabulary": "<vocabulary>"
    },
    "name": "summer_pharmacy_calls_settings_update"
  }
}

Input Schema

NameRequiredDescriptionDefault
companyYes
providerNo
revisionYes
voice_idYes
vocabularyYes
environmentYes
openai_voiceNo
idempotency_keyNoReuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / openai_voice
      Added value: +{
+  "enum": [
+    "alloy",
+    "ash",
+    "ballad",
+    "coral",
+    "echo",
+    "sage",
+    "shimmer",
+    "verse",
+    "marin",
+    "cedar"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / provider
      Added value: +{
+  "enum": [
+    "elevenlabs",
+    "openai_live"
+  ],
+  "type": "string"
+}
  2. Added

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and idempotentHint=false, so the safety profile is partly covered. The description adds useful provider-default behavior and the 'Starts no call' side-effect clarifier, but it omits what existing settings may be overwritten and how revision conflicts are handled.

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 description is short and front-loaded, with each sentence adding some operational context. The first sentence largely restates the title, which is slight redundancy, but the remaining sentences are efficient and purposeful.

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?

This is a destructive settings mutation with eight parameters, low schema description coverage, and no output schema, so the description should explain more about revision expectations, conflict behavior, and the returned result. It clarifies that no call is started and how provider omission behaves, but leaves key mutation semantics incomplete.

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 only 13%, so the description must carry more of the parameter burden. It explains provider defaulting and omitted provider/openai_voice behavior, but gives no meaningful semantics for company, environment, revision, voice_id, or vocabulary beyond the broad purpose sentence.

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: saving the pharmacy-call voice service, voice, and vocabulary at an expected revision. It is clearly distinct from the read-side sibling, though it does not explicitly name alternatives such as phone_calls_settings_update or messenger_voice_update.

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?

Usage is implied by 'Save' and the note that it 'Starts no call,' which clarifies that this is configuration rather than call placement. However, there is no explicit guidance on when to choose this tool over related settings-update siblings or what prerequisites are required.

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