Skip to main content
Glama

SouthPow crypto & market data

buy_tok_HIMSON

Paid. Hims & Hers Health (Ondo Tokenized Stock) (HIMSON) price: live USD price, 24h change and market-cap rank. $0.01 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/price/HIMSON.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and does well: it discloses that the call is paid, the exact price and payment rails, no account/API-key requirement, and that failed calls are not charged. It stops short of documenting rate limits, how payment is authorized, or the full response format beyond the three named metrics.

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 and front-loads the paid nature and the asset/metrics before payment details and the endpoint URL. The telegraphic 'Paid.' opener and dense packing are slightly abrupt, but no sentence is wasted.

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 tool with no output schema, the description provides the asset, returned metrics, cost, payment networks, account requirements, failure policy, and endpoint URL. It could add HTTP method or a fuller response shape, but those are minor omissions given the tool's simplicity.

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?

There are zero input parameters, so there is no parameter meaning for the description to disambiguate. The description correctly treats the asset as fixed, which matches the empty schema; the no-parameter baseline of 4 applies.

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 names the specific asset (Hims & Hers Health / HIMSON) and enumerates the exact data returned: live USD price, 24h change, and market-cap rank. It does not explicitly contrast this tool with the many sibling buy_tok_* tools, but the token symbol makes the target unambiguous.

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?

It supplies useful invocation context: paid, $0.01 USDC on Base or Solana, no account or API key, and failed calls not charged. However, it never states when to choose this over alternatives such as buy_crypto_price or other token-specific price tools, so usage is implied by the asset symbol rather than guided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources