Skip to main content
Glama
Cambrian API MCP

Cambrian API MCP

Official

cambrian_deep42_social_data_influencer_credibility

Filters and ranks crypto social influencers by tweet activity and token-call performance versus Bitcoin, helping assess credibility via accuracy, alpha, reach, and outcomes.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
orderNodesc
handleNo
sort_byNoreturn_vs_bitcoin
min_alphaNo
min_tweetsNo
time_windowNo30d
token_focusNo
include_callsNo
min_outcomes_7dNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv1.10.0
    • addedInput schema / properties / handle
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / include_calls
      Added value: +{
      +  "type": "boolean"
      +}
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +300
    • removedInput schema / properties / min_accuracy_30d
      Removed value: -{
      -  "maximum": 100,
      -  "minimum": 0,
      -  "type": "number"
      -}
    • removedInput schema / properties / min_signals
      Removed value: -{
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • removedInput schema / properties / min_unique_tokens
      Removed value: -{
      -  "minimum": 1,
      -  "type": "integer"
      -}
    • changedInput schema / properties / sort_by / enum
      Previous value: -[
      -  "influence",
      -  "credibility",
      -  "return_vs_bitcoin",
      -  "win_rate_vs_bitcoin",
      -  "tweets",
      -  "engagement",
      -  "reach",
      -  "alpha",
      -  "accuracy",
      -  "conservative_accuracy"
      -]New value: +[
      +  "return_vs_bitcoin",
      +  "win_rate_vs_bitcoin",
      +  "accuracy",
      +  "conservative_accuracy",
      +  "tweets",
      +  "alpha",
      +  "engagement",
      +  "reach"
      +]
    • removedInput schema / properties / track_record_required
      Removed value: -{
      -  "type": "boolean"
      -}
  2. First observedv1.6.0

TDQS

D1/5.0
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Deploy Server

Other Tools