agentweb-mcp

agent_favorites

Retrieve the agent's implicit favorites: businesses it has interacted with more than once, sorted by interaction frequency, for repeat lookups.

Instructions

Get this agent's implicit favorites — businesses it has interacted with more than once. Sorted by interaction frequency. Useful for 'my usual places' or repeat lookups.

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

Input Schema

Name	Required	Description	Default
`limit`	No	Max favorites to return (default: 20, max: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.17.0Jun 21, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations exist, but description clearly indicates read-only behavior (implicit favorites, sorted by frequency). No contradictions.

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

Conciseness5/5

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

Two efficient sentences: first defines purpose, second adds use case. No wasted text.

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?

For a simple tool with one parameter and no output schema, the description fully covers what, how, and when.

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?

Only parameter 'limit' has 100% schema coverage; description adds no new meaning beyond the schema.

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 retrieves 'implicit favorites' based on repeated interactions, sorted by frequency. It distinguishes from sibling tools like agent_history (all history) and get_business (specific business).

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?

Description provides a use case ('my usual places') but does not explicitly state when to avoid or compare with alternatives like agent_history or search_businesses.

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