Skip to main content
Glama

Binary Session

binary_session
Read-onlyIdempotent

Reports current binary target, provider, capabilities, client features, analysis state, and server identity without starting analysis. Use it to check session readiness and reject stale inputs.

Instructions

Report the complete current target, provider, capability availability, client-feature, analysis, and server-identity status without starting analysis.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "binary_session"
  }
}

Input Schema

NameRequiredDescriptionDefault
expected_server_pathNoAbsolute local filesystem path expected for the running server; relative paths are rejected.
expected_catalog_digestNoExpected catalog digest used to reject stale or mismatched input.
expected_package_versionNoExpected package version used to reject stale or mismatched input.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety bar is low; the description still adds real behavior by promising it reports status "without starting analysis," i.e. it will not initialize a session. It also enumerates the reported dimensions, which substitutes for the missing output schema.

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

Conciseness5/5

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

A single front-loaded sentence with no filler; the verb and the no-side-effect constraint come first, followed by the reported contents. Nothing could be removed without losing information.

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?

With no output schema, the enumeration of target/provider/capability/client-feature/analysis/server-identity is what makes the return value predictable, and it covers that job well. The gap is the unmentioned expected_* preconditions and their rejection semantics, which an agent must discover from the schema alone.

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% and each of the three expected_* parameters already carries its own description of mismatch-rejection behavior. The tool description says nothing about these preconditions or what happens when a supplied value does not match, so it adds no meaning beyond the schema — baseline 3.

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 ("Report") plus the resource (current target, provider, capability, analysis and server-identity status), which is clear enough for an agent to know this is a status/introspection call. It also implicitly contrasts with session-starting siblings via "without starting analysis," though it never names an alternative such as open_binary or frida_session_status.

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?

"Without starting analysis" implies the useful condition — check state before acting, with no side effects. There is no explicit when-not guidance and no named alternative among the many sibling status/session tools, so the choice is left partly to inference.

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