Skip to main content
Glama
Sign In

Altss Public Profiles

by io.github.altss-data
OverviewDiscussionsAdmin

Find published Altss profiles

search_public_profiles
Read-onlyIdempotent

Search published organization profile names. Supply a name, 2–120 characters; limit is 1–10, default 5. Returns a bounded ranked subset and canonical citations, not a complete inventory.

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": {
      "query": "<query>"
    },
    "name": "search_public_profiles"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum public profiles to return, 1–10; defaults to 5.
queryYesOrganization name to search among published profiles, 2–120 characters. Results are a bounded ranked subset.

Output Schema

NameRequiredDescriptionDefault
queryYes
scopeYes
resultsYes
citationsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum public profiles to return, 1–10; defaults to 5."
    • addedInput schema / properties / query / description
      Added value: +"Organization name to search among published profiles, 2–120 characters. Results are a bounded ranked subset."
    • addedOutput schema / properties / results / items / 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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, and non-destructive behavior. The description adds useful expectation-setting by saying results are a bounded ranked subset with canonical citations and are not a complete inventory, though it does not explain ranking criteria.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact, front-loaded with the core action, and the result-scope limitation is clearly placed at the end. Some parameter constraints duplicate the schema, which is minor but prevents a top score.

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 simple two-parameter search tool with rich annotations, complete schema descriptions, and an output schema, the description supplies the essential scope and expectation information. Sibling routing is the only notable gap.

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 both parameters are already well documented. The description restates the name length and limit/default constraints and adds little parameter meaning beyond the schema.

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: search published organization profile names. It also clarifies the result is a bounded ranked subset rather than a complete inventory, which sharpens scope, though it does not explicitly distinguish itself from the sibling read tools by name.

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 by 'Search' and the instruction to supply an organization name, making it clear this is a lookup/discovery call. However, it gives no explicit when-to-use or when-not-to-use guidance versus read_public_profile or read_public_profiles_batch.

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