Skip to main content
Glama
Sign In

Starbelo

by com.starbelo
OverviewDiscussionsAdmin

Get an AI tool

get_tool
Read-only

Look up one AI tool on Starbelo by its name. Returns a short description, category, free-plan flag, Starbelo page URL, up to 3 example cases, and sometimes an affiliate try link.

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

Input Schema

NameRequiredDescriptionDefault
nameYesTool name, for example "ElevenLabs".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / name / description
      Previous value: -"Tool name, e.g. \"ElevenLabs\", \"Submagic\""New value: +"Tool name, for example \"ElevenLabs\"."
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so the description only needs to add return-shape context — and it does, listing description, category, free-plan flag, page URL, up to 3 example cases, and an occasionally present affiliate try link. The "sometimes an affiliate link" qualifier is genuinely useful variability disclosure; what is missing is what happens when no matching tool is found.

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 tight sentences with the core action front-loaded and the return contents second. Every clause carries information; nothing is redundant with the title or schema.

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 one-parameter read tool with no output schema and covering annotations, the description supplies the return shape and its one notable quirk (affiliate link). Only the not-found / partial-match behavior is left unspecified, which is a minor gap at this complexity.

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 single parameter already carries an example ("ElevenLabs"), so the baseline is 3. The phrase "by its name" reinforces exact-name lookup but adds no format, casing, or matching-rule detail 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?

"Look up one AI tool on Starbelo by its name" gives a specific verb (look up), a single-resource scope (one AI tool), and the lookup key (name), which is enough to distinguish it from the case/prompt search siblings. It stops short of naming those siblings explicitly, so the differentiation is implied 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?

Usage is only implied: the singular lookup "by its name" suggests this is for a known tool rather than discovery, and the mention of example cases hints at overlap with search_cases. There is no explicit when-to-use, when-not-to-use, or alternative-tool guidance.

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

All Starbelo 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