Get a structured content summary of a URL (title, H1, description, body text, links) using a Presence identity's session. HTTP runtime: returns structured text. Full visual screenshots available via Playwright upgrade. CALL FORMAT: presence_screenshot({ identity_id: 'uuid', url: 'https://...' })
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL to screenshot/summarize. | |
| identity_id | Yes | Identity whose session to use. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. States return type (structured text) and runtime (HTTP). Mentions using a Presence identity's session; lacks details on prerequisites, errors, or idempotency, but sufficient for core behavior.
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 focused sentences: purpose, output type, call format. No redundancy, essential info front-loaded.
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?
Adequately describes inputs, outputs, and key differentiator (vs visual screenshot). Missing mention of session prerequisite and error cases, but overall sufficient for a simple tool.
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?
Schema descriptions cover 100% of params, but description adds value with call format (uuid, https validation) and clarifies role of identity_id and url beyond schema labels.
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?
Clear verb-result: 'Get a structured content summary of a URL' with explicit elements (title, H1, description, body text, links). Distinguishes from visual screenshots via Playwright mention, defining scope precisely.
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?
No explicit when-to-use or when-not-to-use vs siblings like presence_extract or presence_navigate. Implies usage for text extraction vs visual, but no direct comparison or exclusion criteria.
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.
Many tools have distinct purposes, but there are several overlapping or redundant tools (e.g., leadsignal vs leadsignal_generate, multiple code audit tools, multiple trading proposal/journal tools, and several 'universal' entry points like zambo_help, zambo_ask, zambo_universal). Descriptions help, but the volume creates ambiguity.
Naming conventions vary across prefixes (zambo_, zambot_, axis_, presence_, trading_, etc.), with some tools using single words (weather, translate) and others using verb_noun patterns. Aliases like leadsignal_generate for leadsignal break consistency. While prefixes provide some grouping, the overall pattern is mixed.
125 tools is excessive for a single MCP server, even if the server aims to be a universal stack. This makes it overwhelming for agents to navigate and increases the likelihood of misselection. Many tools could be split into domain-specific servers.
The tool surface is extraordinarily comprehensive, covering agent identity, cross-layer orchestration, code analysis, content generation, legal scanning, lead generation, trading, on-chain data, and more. Nearly any common agent task is supported with multiple tools, leaving few obvious gaps.