Skip to main content
Glama

List pinned MCP servers

list_pins
Read-onlyIdempotent

Displays MCP servers pinned by the toolmoat proxy, including pinned tool counts and pending tool changes awaiting user review; read-only.

Instructions

Shows the MCP servers pinned by toolmoat proxy, how many tools each has pinned and which tool changes are waiting for review. This view is read-only; only the user can accept changes, in a terminal.

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": "list_pins"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
toolYes
serversYes
versionYes
lockfileYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.1
    • addedOutput schema / properties / servers / items / properties / omittedPendingTools
      Added value: +{
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds genuinely new context: pending changes exist and cannot be approved through this tool—only the user can accept them, in a terminal. That prevents an agent from attempting an approval flow that doesn't exist.

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 compact sentences, front-loaded with what is returned and ending with the read-only/approval constraint. Dense but no wasted clauses; the phrase 'pinned by toolmoat proxy' and 'has pinned' is slightly tangled but still parseable.

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?

An output schema exists, so return values need not be explained, and the description covers scope, read-only nature and the approval limitation. For a zero-parameter read tool, this is close to complete; only the absence of sibling routing keeps it from a 5.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies an unfiltered listing of all pinned servers.

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 resource (MCP servers pinned by toolmoat proxy) and the specific contents returned (pinned tool counts and pending tool changes). It's clear what the tool does, though it never names or contrasts itself with the scan_* / list_rules siblings, so the differentiation is only implied by the resource.

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 description says the view is read-only and that changes can only be accepted by the user in a terminal, which implies you use this to inspect state rather than mutate it. But it gives no explicit when-to-use vs. the scan_* or list_rules siblings, nor any trigger conditions.

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

Deploy Server

Other Tools