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.

Remove your own profile photo

summer_account_photo_remove
Destructive

Remove your own profile photo. Replies you send afterward show your initials; earlier replies keep the photo they were sent with.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "summer_account_photo_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
idempotency_keyNoReuse the same key when retrying the same change

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotency, so safety is covered. The description adds real, non-annotation context: after removal, subsequent replies render initials while previously sent replies retain the photo, which clarifies blast radius and non-retroactivity of the change.

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?

Two tight sentences: the action first, then the consequence. No filler, no repetition of the title, and the most decision-relevant effect is front-loaded in the second sentence.

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?

For a single-optional-parameter mutation with no output schema, this covers action and visible consequence well. It stops short of stating whether a removed photo can be restored or what happens if no photo exists, which are the remaining gaps an agent might care about.

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?

Only one optional parameter and schema coverage is 100%, so the schema already fully documents idempotency_key. The description adds no additional semantics about retry behavior, which is a minor missed opportunity given annotations mark the tool non-idempotent.

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 verb and resource ('Remove your own profile photo') with an explicit scope constraint ('your own') that separates it from teammates or company-level account tools. An agent knows exactly what is being changed without opening the schema.

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 'own' qualifier implies this is only for the calling user's photo, which is useful routing signal. However it never states preconditions (e.g. that a photo must currently exist), or points at any alternative for viewing/updating a photo instead of removing it.

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