Skip to main content
Glama

ask_tensorfeed

Ask TensorFeed a plain-language question about AI models, providers, or AI security and get the answer itself, not a list of endpoints. Answers from free live data: the best or cheapest model for a task (coding, reasoning, writing), one model's price, context window, and specs, two models side by side, whether an AI provider or service is down right now, the latest AI news on a topic, upcoming model deprecations and shutdowns, and CVE or CISA KEV lookups including AI packages like vllm. Returns answer (one or two sentences), data (the supporting slice), sources (endpoint plus a tensorfeed.ai page_url to cite), next (1 to 3 follow-up calls; paid ones carry their price and what they add), intent, and confidence. When no direct answer applies it says so and returns the best-matching TensorFeed tools and endpoints instead. Free, no auth. Examples: "cheapest model for coding with vision", "is OpenAI down right now?". Use this first for any AI model, pricing, status, news, or security question.

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

Input Schema

NameRequiredDescriptionDefault
questionYesThe question in plain language, up to 300 characters. Name models, providers, packages, or CVE ids the way you would to a person, e.g. "How much does Claude Opus 5.5 cost?" or "Is CVE-2024-3094 in CISA KEV?".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: free, no auth, answers drawn from live data, answer length (one or two sentences), the exact response shape, and that suggested follow-ups may be paid with price shown. It also discloses the miss behavior, returning best-matching tools instead of failing silently.

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?

Front-loaded with what it does and what it returns, with the long capability enumeration and routing instruction placed after. Dense but mostly earning its place; the capability list and return-field list are somewhat redundant with each other but useful for matching question types.

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?

No output schema exists, so the description compensates by naming every returned field (answer, data, sources, next, intent, confidence) and what sources contain (endpoint plus a citable page_url). Combined with auth and fallback behavior, an agent has everything needed to call it and interpret results.

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 coverage is 100% and the single parameter already documents the 300-character limit and example phrasings, so the description adds little new parameter guidance. Its 'name models, providers, packages, or CVE ids the way you would to a person' phrasing echoes the schema rather than extending it; baseline 3 is appropriate.

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?

States a specific verb and resource ('Ask TensorFeed a plain-language question about AI models, providers, or AI security') and explicitly contrasts the outcome with sibling list tools ('the answer itself, not a list of endpoints'). The enumerated domains (pricing, status, news, deprecations, CVE/KEV) make the scope unambiguous.

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

Usage Guidelines5/5

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

Gives an explicit routing rule: 'Use this first for any AI model, pricing, status, news, or security question,' and the not-a-list phrasing steers enumeration tasks to sibling tools. It also documents the fallback path when no direct answer applies, which tells the agent what to do on a miss.

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.