Skip to main content
Glama

saagarpatel.dev Portfolio

List repo profiles

list_repo_profiles
Read-only

List public-safe repo answering profiles with repo id, attention state, freshness, and proof counts. Profiles are static artifacts baked from saagarpatel.dev, not live repo health.

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax profiles
attentionStateNoFilter by attention state, e.g. "active-infra" or "decision-needed"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Added

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 and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious behavior: the data is static, baked from saagarpatel.dev, and explicitly not live repo health — which prevents an agent from misreading freshness as real-time status.

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 with zero filler, and the most decision-relevant content (what it lists, what fields come back) is front-loaded before the static-artifact caveat.

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?

There is no output schema, so the description correctly compensates by naming the returned fields, and it discloses the data-provenance caveat. For a simple two-optional-param read tool with read-only annotations, this is close to complete; only explicit sibling routing is missing.

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?

Schema coverage is 100% and both parameters (limit with min/max, attentionState with example values) are documented in the schema itself. The description adds no parameter-level detail beyond listing the returned fields, so the baseline of 3 applies.

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 uses a specific verb and resource ("List public-safe repo answering profiles") and enumerates the fields each profile carries (repo id, attention state, freshness, proof counts). It is clearly a collection-listing counterpart to the singular get_repo_profile, though it never names that sibling 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: "List" plus the "public-safe" qualifier signals this is the enumeration path, and the note that profiles are static artifacts warns against treating them as live health data. However, there is no explicit routing guidance such as "use get_repo_profile for a single repo" or when to prefer list_corpus/list_projects instead.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.