Skip to main content
Glama
Sign In

AgentViva

by dev.agentviva
OverviewDiscussionsAdmin

Is this AI tool up?

lookup_tool
Read-only

Look up an AI tool AgentViva already watches publicly, by name ("Notion") or address ("notion.so"), and get its state (up, degraded, down, blocked or unknown), since when, and its public status page. No API key needed. It reads what AgentViva already knows; it does not check the address now.

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": {
      "query": "<query>"
    },
    "name": "lookup_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesA tool name or an address.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description carries most of the burden and does well: it discloses that results come from already-known cached data rather than a live probe, that no credential is required, and what fields come back (state, since when, status page). It does not cover behavior when nothing matches or whether results are rate limited.

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?

Three front-loaded sentences with the core lookup described first and constraints after. There is mild redundancy between 'reads what AgentViva already knows' and 'does not check the address now', but both add distinct nuance (data origin vs. no live probe).

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 read tool with no output schema, the description adequately explains inputs, the meaning of the result, and staleness semantics. The only gap is the behavior on no-match, only partially covered by the listed 'unknown' state.

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% with a bare 'A tool name or an address', so baseline is 3; the description earns an extra point by giving concrete input forms ('Notion' vs 'notion.so') that show the two accepted shapes the schema only summarizes.

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?

States a specific verb (look up) and resource (an AI tool) plus the scoping constraint 'AgentViva already watches publicly', and enumerates the returned state values. The closing clause 'it does not check the address now' implicitly separates it from a live-check sibling such as check_url.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The negative constraint 'it does not check the address now' tells an agent when this tool is the wrong choice, and 'no API key needed' clarifies the access precondition. It stops short of naming the alternative tool to use for a live check, leaving that inference to the agent.

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

All AgentViva toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources