Skip to main content
Glama
Sign In
fuzzmind-frida-mcp

fuzzmind-frida-mcp

by fuzzmind
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

frida_portal_narrowcast

Send a targeted message to portals matching a specified tag, enabling narrowcast communication for dynamic analysis and security research.

Instructions

Narrowcast a message by PortalService tag.

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": {
      "portal_id": "<portal_id>",
      "tag": "<tag>",
      "message": "<message>"
    },
    "name": "frida_portal_narrowcast"
  }
}

Input Schema

NameRequiredDescriptionDefault
portal_idYes
tagYes
messageYes
data_base64No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.2/5.0
Behavior1/5

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

No annotations are provided, so the description carries full burden. It does not disclose side effects, authorization needs, idempotency, or any behavioral traits beyond the basic action. For a tool that sends messages, this is a critical gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence, which is concise but too brief. It lacks necessary details to be useful, so it sacrifices completeness for brevity.

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

Completeness1/5

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

Given no output schema, no parameter descriptions, and no annotations, the description is vastly incomplete. An agent cannot reliably select or invoke this tool without additional context.

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

Parameters1/5

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

Schema description coverage is 0%, meaning the description adds no meaning to the parameters. The parameters portal_id, tag, message, and data_base64 are not explained, leaving the agent to guess their purposes and formats.

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 the action (narrowcast a message) and the resource (PortalService tag), distinguishing it from sibling tools like broadcast. However, it could be more specific about what 'narrowcast' means and what 'PortalService tag' exactly refers to.

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

Usage Guidelines2/5

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

No guidance on when to use narrowcast versus broadcast or post, or any prerequisites or context. The agent is left to infer usage from the name alone.

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