Skip to main content
Glama

BRAINIAC OSINT & Digital Evidence Forensics

Extract visual location clues

evidence-intelligence_visual-location-clue-extract

Extract embedded GPS or location text clues from local image metadata. Missing coordinates are not invented. Price $0.04 USDC. POST /api/v1/evidence-intelligence/visual-location-clue-extract. Unpaid calls return 402 and do not run.

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": "evidence-intelligence_visual-location-clue-extract"
  }
}

Input Schema

NameRequiredDescriptionDefault
csvNo
asOfNo
jsonNo
textNo
filesNo
custodyEventsNo
expectedHashesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: missing coordinates are not fabricated, the call costs $0.04 USDC, and unpaid calls return 402 without executing. It omits what is actually returned (fields, confidence), size or media-type limits, and whether the operation is idempotent. The billing and failure semantics are genuinely valuable additions beyond structured data.

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?

Four short sentences, front-loaded with the core purpose and the no-fabrication guarantee. Pricing and endpoint details are compact and non-redundant. Nothing is padded, though it is arguably under-specified rather than efficiently concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a seven-parameter tool with no annotations, no output schema, and zero schema description coverage, the description is too thin. It never explains the accepted payload shapes (base64 files, custody events, expected hashes) or the return structure, so an agent cannot construct a correct call from this text alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Seven parameters at 0% schema description coverage, and the description explains none of them. The roles of csv, json, text, asOf, custodyEvents, and expectedHashes are entirely undefined, and even the relationship between 'files' and 'local image metadata' is unstated. This is a significant gap the description should have filled.

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?

States a specific verb and resource: 'Extract embedded GPS or location text clues from local image metadata.' An agent knows the operation and the source data type. It does not differentiate itself from the sibling metadata-extract tool, which likely overlaps, so it falls short of a 5.

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?

Implies the use case (images carrying location clues) via 'from local image metadata,' but never says when to prefer this over evidence-intelligence_metadata-extract or what inputs qualify. No exclusions or prerequisites are stated, leaving selection largely to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources