Skip to main content
Glama
Sign In
underindex-mcp

underindex-mcp

by ascanioUnderIndex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Free sample record

get_sample_record

Fetch one complete free sample UnderIndex record in the same shape as full subculture records to preview what a record contains before paying for others.

Instructions

Return one complete UnderIndex record (Goth Ninja) for free, in exactly the shape get_subculture returns. Use it to see what a record contains before paying for others.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose the two non-obvious traits: the call is free while siblings are paywalled, and the payload is a single fixed sample rather than a queryable selection. It does not mention rate limits, whether the sample is stable across calls, or that it is a read-only non-mutating call.

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 sentences, no filler, and the payoff statement (what you get) is front-loaded ahead of the reason to use it. Nothing could be deleted without losing information.

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?

For a zero-parameter preview tool with no output schema, the description covers cost, cardinality, content, and output shape by reference to a sibling. It omits only minor details such as whether repeated calls return identical data or whether the sample is subject to limits.

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 no argument semantics to convey and the schema is trivially complete. Baseline 4 applies; the description correctly implies the sample is fixed and therefore not parameterizable.

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?

States a specific verb and resource ("Return one complete UnderIndex record") and pins down the content (Goth Ninja) and its equivalence to get_subculture's output shape. An agent can tell it apart from the paid sibling without opening any schema.

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

Usage Guidelines4/5

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

"Use it to see what a record contains before paying for others" gives a clear triggering condition and implicitly contrasts it with the paid retrieval path. It stops short of an explicit exclusion (e.g., do not use this when you need a record for a specific subculture).

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