Skip to main content
Glama
Sign In

Summer

by ai.gosummer
OverviewDiscussionsAdmin

Get the Summer browser URL for a company administrator to install and authorize the Summer GitHub App

summer_github_connection_start
Read-onlyIdempotent

Get the Summer browser URL for a company administrator to install and authorize the Summer GitHub App. Code access is read-only; issue handoffs use separate GitHub Issues permission and exact case approval. Does not grant access or connect an installation by itself.

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

Input Schema

NameRequiredDescriptionDefault
companyYes
environmentYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds real context beyond that: code access is read-only, issue handoffs require a separate GitHub Issues permission with exact-case approval, and the call has no side effect of its own — it does not grant access or create an installation.

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?

Three short sentences, with the core action front-loaded and the permission caveat following. The phrase 'exact case approval' is slightly opaque and costs a bit of clarity, but there is no filler.

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?

For a read-only URL-fetch tool with no output schema, the description covers the action and its non-effects, but leaves the caller guessing about parameter meaning (especially which environment to pick) and what the returned URL includes or how long it is valid.

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 the burden for the two required parameters, yet it never mentions 'company' or 'environment'. It gives no indication that company is the target tenant UUID or how the staging vs. production enum affects the URL returned.

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?

States a specific verb and artifact: returns a browser URL that lets a company administrator install and authorize the Summer GitHub App. The final sentence ('Does not grant access or connect an installation by itself') distinguishes it from the actual connection-mutating siblings (github_connection_disconnect, github_connection_read), though no sibling is named explicitly.

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 rather than stated: this is the setup/start step an admin follows before an installation exists, and the note that handoffs need a separate GitHub Issues permission hints at prerequisites. There is no explicit 'call this when…' or 'use X instead when…' guidance against the several github_* 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