Skip to main content
Glama

get_pricing

Retrieve current pricing, network configuration, and wallet address for Intelica API. Verify costs before making calls.

Instructions

Returns current pricing, available endpoints, network configuration, and wallet addresses for the Intelica API.

Free to call — no payment required.

Returns a JSON object with:

  • single (object): Pricing for POST /intel (single analysis)

    • price (str): "$0.05 USDC"

    • max_items (int): 1

  • batch (object): Pricing for POST /batch (batch analysis)

    • price (str): "$0.20 USDC"

    • max_items (int): 10

  • demo (object): Pricing for POST /demo (free demo)

    • price (str): "free"

    • limit (str): "300 chars, no URL"

  • network (str): Payment network in CAIP-2 format ("eip155:8453" = Base mainnet)

  • pay_to (str): EVM wallet address receiving payments

  • asset (str): Payment asset ("USDC")

  • protocol (str): Payment protocol ("x402")

Use this tool to:

  • Verify current prices before making calls

  • Get the wallet address for manual payment verification

  • Confirm network and asset configuration

Example usage: get_pricing()

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It states it's free to call and details the return structure with examples. This adds significant behavioral context beyond the empty schema.

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 well-structured with bullet points and clear sections. While slightly verbose with full output examples, it remains focused and front-loads the purpose. Could be trimmed slightly.

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?

Given no parameters and no annotations, the description is fully complete. It explains the entire JSON output structure with types and example values, leaving no ambiguity for the agent.

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?

Zero parameters, so baseline is 4. The description does not need parameter elaboration. Schema coverage is 100% vacuously.

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?

The description clearly states the tool returns pricing, endpoints, network config, and wallet addresses. It distinguishes itself from analysis sibling tools by being informational. The verb 'get' and resource 'pricing' are specific.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description lists explicit use cases: verify prices, get wallet address, confirm network/asset. No exclusions are needed since it's a unique informational tool. The guidance is clear but could mention when not to use (e.g., no pricing needed).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/teodorofodocrispin-cmyk/intelica-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server