Skip to main content
Glama
Sign In
TEOS Agent Tools

TEOS Agent Tools

by threebeats
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

summarize_url

Fetch a web page and return a short summary with its title and source URL to help users understand content without reading it all.

Instructions

Fetch a web page and return a short summary with its title and source. Paid. Returns title, summary, source_url.

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": {
      "url": "<url>"
    },
    "name": "summarize_url"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesPage URL to summarize

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses the cost model ('Paid') and the returned fields, which is meaningful context, but says nothing about auth requirements, rate limits, latency, or failure behavior for unreachable pages.

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?

The description is short and front-loaded with the core action, and 'Paid' is surfaced early. There is mild redundancy between 'with its title and source' and 'Returns title, summary, source_url.'

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 single-parameter tool with no output schema, the description covers the essential behavior and enumerates the returned fields, which compensates for the missing output schema. It is adequate, though cost/return details could be slightly clearer.

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?

There is a single parameter and schema description coverage is 100%, so the schema already documents the URL input. The description adds no format or constraint detail beyond the schema, which is the expected baseline when the schema does the work.

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?

The description states a specific verb and resource: fetch a web page and return a short summary with title and source. It is clearly distinguishable from siblings like extract_keyphrases or verify_claim by virtue of being a summarizer, but it never names or contrasts those alternatives explicitly.

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?

The only usage signal is the terse 'Paid' flag, which usefully warns of a cost before invocation. There is no guidance on when to prefer this over sibling tools (extract_keyphrases, verify_claim) or any prerequisites, so usage is only implied.

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

Deploy Server

Other Tools