Summer

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.

List repositories available to this company GitHub installation

summer_github_repositories_list

Read-onlyIdempotent

List repositories available to this company GitHub installation. Provider metadata read; no file content.

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

Input Schema

Name	Required	Description	Default
`page`	No
`company`	Yes
`environment`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 23, 2026

TDQS

C2.9/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description adds real value with 'Provider metadata read; no file content', clarifying that UIs/agents should not expect code or file payloads. It is silent on pagination behavior (the page param implies paging), result caps, or auth prerequisites, which keeps it at 3.

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?

Two short sentences with the scope front-loaded and no waste. The second sentence is a terse fragment ('Provider metadata read') that is slightly cryptic but still earns its place by delimiting output content.

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?

No output schema, no annotation-level explanation, and 0% param coverage mean the description should do more. It never explains pagination behavior, what 'repositories available' means in terms of installation vs user scope, or what a page of results looks like, leaving the agent guessing on invocation details.

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 all three parameters (company UUID, environment enum, page) rely on the schema shape alone. The description's 'this company GitHub installation' weakly maps to the company parameter but says nothing about environment (staging vs production) or page semantics, so it does not compensate for the coverage gap.

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?

Specific verb (List) and resource (repositories) scoped to 'this company GitHub installation', which separates it from siblings like summer_github_folders_list and summer_github_sources_read without naming them. The scope is precise enough that an agent can identify the operation, though no sibling is explicitly called out.

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

Usage Guidelines2/5

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

No statement of when to use this versus the other GitHub tools (folders_list, sources_read, connection_read). 'No file content' hints at a negative boundary but doesn't route the agent to an alternative for fetching code or file metadata.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Summer tools Inspect

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

Need Help?