todays_featureReturns today's featured business (rotates daily): one full profile, same shape as get_business. Example: {} -> one business record. Cost: free (100 calls/day without a key).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections.
Output schema / properties / result / oneOfPrevious value: -[
- {
- "additionalProperties": true,
- "properties": {
- "annualized_revenue_basis": {
- "type": [
- "string",
- "null"
- ]
- },
- "annualized_revenue_usd": {
- "type": [
- "number",
- "null"
- ]
- },
- "badge_plain_url": {
- "type": "string"
- },
- "badge_url": {
- "type": "string"
- },
- "business_model": {
- "type": [
- "string",
- "null"
- ]
- },
- "category": {
- "type": "string"
- },
- "confidence": {
- "type": [
- "string",
- "null"
- ]
- },
- "founded": {
- "type": [
- "string",
- "null"
- ]
- },
- "growth_series": {
- "type": "array"
- },
- "lessons": {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "metrics": {
- "items": {
- "additionalProperties": true,
- "type": "object"
- },
- "type": "array"
- },
- "name": {
- "type": "string"
- },
- "one_liner": {
- "type": [
- "string",
- "null"
- ]
- },
- "related": {
- "items": {
- "additionalProperties": true,
- "type": "object"
- },
- "type": "array"
- },
- "revenue_disclosed": {
- "type": "boolean"
- },
- "slug": {
- "type": "string"
- },
- "source_sync_stale_since": {
- "type": [
- "string",
- "null"
- ]
- },
- "tier": {
- "type": "string"
- },
- "url": {
- "type": "string"
- },
- "url_profile": {
- "type": "string"
- },
- "what_the_agent_does": {
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "slug",
- "name",
- "metrics",
- "url_profile"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
-]New value: +[
+ {
+ "additionalProperties": true,
+ "properties": {
+ "annualized_revenue_basis": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "annualized_revenue_usd": {
+ "type": [
+ "number",
+ "null"
+ ]
+ },
+ "badge_plain_url": {
+ "type": "string"
+ },
+ "badge_url": {
+ "type": "string"
+ },
+ "business_model": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "category": {
+ "type": "string"
+ },
+ "confidence": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "founded": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "growth_series": {
+ "type": "array"
+ },
+ "lessons": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "metrics": {
+ "items": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "name": {
+ "type": "string"
+ },
+ "one_liner": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "referral": {
+ "type": "boolean"
+ },
+ "related": {
+ "items": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "revenue_disclosed": {
+ "type": "boolean"
+ },
+ "signup_go_url": {
+ "description": "Same link via mrrledger.com/go/<slug> (counts the click, then 302)",
+ "type": "string"
+ },
+ "signup_url": {
+ "description": "Referral link (only on businesses with one). Always shown with signup_url_disclosure; never affects figures, ranking, sorting or verification.",
+ "type": "string"
+ },
+ "signup_url_disclosure": {
+ "type": "string"
+ },
+ "signup_url_label": {
+ "type": "string"
+ },
+ "slug": {
+ "type": "string"
+ },
+ "source_sync_stale_since": {
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "tier": {
+ "type": "string"
+ },
+ "url": {
+ "type": "string"
+ },
+ "url_profile": {
+ "type": "string"
+ },
+ "what_the_agent_does": {
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "slug",
+ "name",
+ "metrics",
+ "url_profile"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+]Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only, idempotent, and non-destructive, so the bar is lower, and the description adds real value: daily rotation and a free-tier rate limit (100 calls/day without a key). It does not clarify that repeated calls within a day return the same record, which a careful agent might wonder given the 'rotates daily' phrasing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three short clauses, front-loaded with the return value, then shape, then example, then cost. No wasted text.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists and the description still tells the agent the return shape (same as get_business), plus cost and rotation. Nothing needed to call it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Zero parameters, so the baseline is 4. The '{} -> one business record' example reinforces that the call takes no input, which is a small extra confirmation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Returns today's featured business') and adds the rotation cadence, so the agent knows exactly what it gets. It notes the profile shape matches get_business, which helps orient it against the sibling without explicitly saying when to prefer that sibling.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'rotates daily' framing implies when this is useful (a daily spotlight/discovery call), but there is no explicit when-to-use, when-not, or pointer to get_business for a specific record. The 100 calls/day limit is a soft usage hint but not selection guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.