Skip to main content
Glama
Sign In

Altss Public Profiles

by io.github.altss-data
OverviewDiscussionsAdmin

Read a published Altss profile

read_public_profile
Read-onlyIdempotent

Read one published profile by its public slug. Returns a limited public summary and canonical citation. Follows published aliases. Does not expose private contacts or underlying warehouse records.

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": {
      "slug": "<slug>"
    },
    "name": "read_public_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesPublic profile slug from a search result or canonical /profile/{slug} URL; supply the slug only, not a URL.

Output Schema

NameRequiredDescriptionDefault
profileYes
citationsYes
dateMeaningYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / slug / description
      Added value: +"Public profile slug from a search result or canonical /profile/{slug} URL; supply the slug only, not a URL."
    • addedOutput schema / properties / profile / properties / slug / description
      Added value: +"Public profile slug from a search result or canonical /profile/{slug} URL; supply the slug only, not a URL."
  2. Changed2 schema fields changed
    • addedOutput schema / properties / profile / properties / yearFounded / maximum
      Added value: +9007199254740991
    • addedOutput schema / properties / profile / properties / yearFounded / minimum
      Added value: +-9007199254740991
  3. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral context beyond them: alias resolution, the privacy boundary (no private contacts, no warehouse records), and the limited nature of the returned summary.

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, front-loaded with the verb and resource, then return shape, then exclusions. No redundant wording and nothing buried.

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?

With one well-documented parameter, rich annotations, and an output schema covering return values, the description needs only to add scope and privacy boundaries, which it does. It could be slightly stronger by noting what happens with unpublished or unknown slugs, but it is otherwise complete.

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%, and the schema already explains that the slug must be supplied bare rather than as a URL, with format constraints. The description adds nothing about the slug beyond restating the resource it identifies, so the baseline of 3 applies.

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 ('Read one published profile by its public slug') and scopes it to a single record, which implicitly separates it from the batch reader and the search tool. An agent can tell this is the by-slug single-record retrieval path without opening the schema.

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 only implied: the tool retrieves a known slug, and the schema hints the slug comes from a search result or canonical URL. The description never explicitly says when to use this versus search_public_profiles or read_public_profiles_batch, leaving the routing inference to the agent.

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