Skip to main content
Glama

psa_population_report

Retrieve PSA card certification details and complete population reports showing grade distribution from Auth through PSA 10 for accurate market analysis.

Instructions

Look up PSA card certification details and full population report. Returns card info (year, brand, subject, grade) and complete grade breakdown from Auth through PSA 10, showing how many cards exist at each grade level.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
certNumberNoPSA certification number printed on the slab (e.g. "10000001")
specIDNoPSA spec ID for direct population lookup (advanced, from cert lookup)

Implementation Reference

  • The registration and handler implementation for the psa_population_report tool. It defines the parameters (certNumber, specID) and fetches data from a backend URL.
    server.tool(
      "psa_population_report",
      "Look up PSA card certification details and full population report. Returns card info (year, brand, subject, grade) and complete grade breakdown from Auth through PSA 10, showing how many cards exist at each grade level.",
      {
        certNumber: z
          .string()
          .optional()
          .describe('PSA certification number printed on the slab (e.g. "10000001")'),
        specID: z
          .number()
          .int()
          .optional()
          .describe("PSA spec ID for direct population lookup (advanced, from cert lookup)"),
      },
      async ({ certNumber, specID }) => {
        const params = new URLSearchParams();
        if (certNumber) params.set("certNumber", certNumber);
        if (specID) params.set("specID", String(specID));
    
        const url = `${BACKEND_URL}/psa/pop?${params.toString()}`;
        const res = await fetch(url);
        const data = await res.json();
    
        if (!data.success) {
          return {
            isError: true,
            content: [{ type: "text", text: `Error: ${data.error}` }],
          };
        }
    
        return {
          content: [{ type: "text", text: JSON.stringify(data, null, 2) }],
        };
      }
    );
Behavior3/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It clarifies that the tool returns card details and a grade breakdown, which is useful, but omits critical behaviors like error handling, rate limits, authentication needs, or data freshness. It adequately describes the output but lacks operational context.

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?

The description is front-loaded and efficiently structured in two sentences: the first states the action and resource, the second details the return values. Every sentence adds value without redundancy, making it highly concise.

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?

Given the lack of annotations and output schema, the description partially compensates by explaining the return format. However, it does not address potential errors, input constraints, or how the tool fits into broader workflows, leaving gaps for a tool with two parameters and no structured output documentation.

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 description coverage is 100%, so the schema fully documents both parameters. The description adds no additional meaning beyond what the schema provides, such as usage examples or interdependencies between certNumber and specID. It meets the baseline for high schema coverage.

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?

The description clearly states the specific action ('Look up') and resource ('PSA card certification details and full population report'), distinguishing it from unrelated sibling tools like license verification or marketplace searches. It precisely defines what information is retrieved, making the purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives, such as whether it's for certified cards only or how it differs from other lookup methods. The description focuses solely on what the tool does, not its context or prerequisites.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lulzasaur9192/marketplace-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server