Skip to main content
Glama
Sign In

Altss Public Profiles

by io.github.altss-data
OverviewDiscussionsAdmin

Compare published Altss profiles

read_public_profiles_batch
Read-onlyIdempotent

Read one to five unique public slugs in one bounded call. Returns ordered per-profile 200, 404 or 503 outcomes, limited summaries, canonical citations and date qualifications. No private contacts, record writes or full-inventory export.

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": {
      "slugs": "<slugs>"
    },
    "name": "read_public_profiles_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Output Schema

NameRequiredDescriptionDefault
scopeYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, non-destructive and closed-world, yet the description still adds real value: ordered per-profile outcomes, partial-failure statuses (200/404/503), canonical citations and date qualifications. It also disclaims private contacts and record writes, so an agent knows a mixed-result batch is normal rather than an error.

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?

Three short sentences with no filler: capability first, return shape second, exclusions last. Every clause contributes a distinct fact an agent needs.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read-only batch tool with an output schema already documenting the return shape, this description covers inputs, per-item outcome semantics, and scope limits. Nothing needed to invoke it correctly is missing.

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?

Schema coverage is 0%, but with a single parameter the description carries the burden well: it identifies slugs as unique, public, and between one and five, adding the uniqueness constraint the schema does not encode. It does not restate the slug character pattern, which is a minor omission the schema covers.

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 verb and resource ('Read ... public slugs') plus the batch scope ('one to five ... in one bounded call'), which separates it from the singular read_public_profile. It never names the sibling tools explicitly, so routing is inferred rather than stated.

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 'one to five unique public slugs in one bounded call' phrasing implies the batch use case, and 'No full-inventory export' signals a limit on scope. There is no explicit when-to-use guidance such as using read_public_profile for a single slug or search_public_profiles to discover slugs.

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

All Altss Public Profiles toolsInspect
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