Grandet

Find free API credit / 查找免费 API 额度

grandet_find_free_credits

Read-onlyIdempotent

Find current official free tiers, application-based credits and relay free groups. Return the stated benefit, six requirements, deadline, original observation and claim link. userCanMeet=no_card excludes explicit required/conditional card entries; unknown card requirements remain clearly labelled unknown. Application categories describe programs, not the user’s eligibility. Follow pagination.

Input Schema

Name	Required	Description	Default
`q`	No	Model, vendor or site to search, e.g. "gemini".
`asOf`	No	Evaluate as of this UTC time (ISO 8601, e.g. "2026-10-16T12:00:00Z"). Omit to evaluate now.
`host`	No	The assistant or app making this call, e.g. "claude-code" or "codex". Attribution only; it does not change results.
`kind`	No	"official" free tiers and credits, "relay" free groups, or "all".
`lang`	No	Answer language: "en" or "zh-CN".	en
`page`	No	Result page, starting at 1.
`view`	No	"compact" (default): about 18 KB for a typical query. "full": every field, often over 250 KB.	compact
`limit`	No	Results per page, 1–20.
`targetApp`	No	Catalogue ID of the app that will use the API, e.g. "openclaw", "claude-code" or "codex". Selects compatible protocols and connection steps. Send it only when the user says where the API will be used.
`releaseSet`	No	Pin a published data release by its release-set hash. Omit to use the current release.
`skillBuild`	No	Grandet Skill build ID when called from the Skill. Omit otherwise.
`userCanMeet`	No	Only offers the user can meet: "any", "no_card" (no payment card) or "student".
`skillVersion`	No	Grandet Skill version when called from the Skill, e.g. "0.3.0". Omit otherwise.

Output Schema

Name	Required	Description	Default
`help`	No
`total`	No
`offers`	No
`schema`	No
`coverage`	No
`qualification`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 18, 2026

addedInput schema / properties / skillBuild / maxLength
```
Added value: +256
```
removedInput schema / properties / skillBuild / pattern
```
Removed value: -"^[a-zA-Z0-9._-]{1,96}$"
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "coverage": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "help": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "offers": {
+      "items": {},
+      "type": "array"
+    },
+    "qualification": {
+      "additionalProperties": {},
+      "type": "object"
+    },
+    "schema": {
+      "type": "string"
+    },
+    "total": {
+      "type": "number"
+    }
+  },
+  "type": "object"
+}

First observedOct 17, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description earns credit above that by disclosing what a result contains (stated benefit, requirements, deadline, observation, claim link) and how pagination behaves, though it says nothing about rate limits or freshness guarantees of the catalogue.

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 the purpose and then moves straight into filter semantics and pagination with no filler sentences. Slightly dense and telegraphic in places, which costs it a perfect score, but every sentence carries information.

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 13-parameter, optional-argument search tool with an output schema present, the description covers purpose, the two non-obvious filter semantics and pagination — the items an agent is most likely to get wrong. Return-value explanation is redundant given the output schema, and no gaps materially block correct invocation.

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?

Schema coverage is 100%, so the baseline is 3, but the description genuinely adds meaning beyond the schema: it explains that userCanMeet=no_card excludes explicit required/conditional card entries while unknown card requirements stay labelled unknown, and that application categories describe programs rather than user eligibility. That clarifies filter semantics the schema leaves ambiguous.

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?

States a specific verb ('Find') and a well-scoped resource ('official free tiers, application-based credits and relay free groups'), which is clearly distinct from grandet_find_cheapest_api and the resolver/glossary siblings. It doesn't name an alternative sibling explicitly, so it falls short of a 5.

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 gives conditional guidance for the no_card filter and tells the agent to 'Follow pagination', which is real usage direction, but never says when to choose this tool over grandet_find_cheapest_api or grandet_quote_evidence. Usage is implied rather than contrasted with alternatives.

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

All Grandet tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.