HALO (GEMMA-by-GOOGLE)

Overview Schema Source Related Servers Discussions Admin

run_phoneinfoga

Perform OSINT footprinting on a phone number to identify carrier, region, and formatting. Use this tool to gather intelligence from a phone number for security assessments.

Instructions

OSINT footprinting of a phone number (carrier, region, formatting).

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": {
      "number": "<number>"
    },
    "name": "run_phoneinfoga"
  }
}

Input Schema

Name	Required	Description	Default
`number`	Yes	Phone number in international format.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 10, 2026

TDQS

B3.4/5.0

Behavior2/5

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

With no annotations, the description carries full burden but only offers a high-level overview ('footprinting'). It fails to disclose details like network requests, output format, or any potential side effects. The word 'footprinting' is vague and does not clarify read-only vs. active reconnaissance.

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 a single sentence that immediately conveys the core purpose. It is efficient and front-loaded, though it could be slightly more informative without sacrificing conciseness.

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

Completeness3/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 is minimally adequate. However, it lacks context on what exactly the output contains, how the tool behaves (e.g., live query vs. local database), and any usage constraints.

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?

Schema coverage is 100% for the single parameter 'number', which has a clear description ('Phone number in international format'). The description adds no additional meaning beyond the schema, so baseline score of 3 is appropriate.

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 'OSINT footprinting of a phone number' and specifies the key outputs (carrier, region, formatting). It uniquely identifies the tool's purpose and distinguishes it from sibling tools like run_sqlmap or run_nmap which target different resource types.

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 description implies use for phone number investigation but provides no explicit guidance on when to use versus alternatives (e.g., run_sherlock for usernames, run_shodan for IPs). There is no mention of when not to use the tool or prerequisites.

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