Skip to main content
Glama

Verify Managed Native Boundaries

verify_managed_native_boundaries
Idempotent

Verify managed P/Invoke and native-boundary declarations against authenticated native export/function evidence without executing managed code; preserve verification states.

Instructions

Verify managed P/Invoke/native-boundary declarations against authenticated native export or function Evidence without executing managed code or translating managed metadata tokens into native addresses. The workflow preserves declaration-only, verified, inferred, contradicted, and unresolved states.

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": {
      "managed_boundaries": "<managed_boundaries>",
      "native_observations": "<native_observations>"
    },
    "name": "verify_managed_native_boundaries"
  }
}

Input Schema

NameRequiredDescriptionDefault
managed_boundariesYes
native_observationsYesNative function or export Evidence records

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral constraints beyond that: it does not execute managed code, does not translate managed metadata tokens into native addresses, and preserves specific verification states. It still does not clarify why the tool is not read-only or what side effects may occur, but the added constraints are meaningful.

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 only two sentences and front-loads the core action and scope. The second sentence about preserved states is relevant and compact. It is dense with domain jargon, but there is no filler or unnecessary repetition.

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 complex verification tool with a large nested input schema and no output schema, the description covers the core operation and behavioral constraints reasonably well. It remains incomplete on usage versus sibling tools and on parameter-level guidance for the two required inputs. The mention of verification states partially compensates, but an agent still lacks routing and input-shape clarity.

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?

The schema has only 2 top-level parameters and 50% description coverage. The description conceptually maps 'managed P/Invoke/native-boundary declarations' to the managed-boundary input and 'native export or function Evidence' to native observations. That is useful, but it does not explain the required evidence structure or the meaning of key fields such as evidence_id, authority, or confidence.

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 uses a specific verb and resource: 'Verify managed P/Invoke/native-boundary declarations against authenticated native export or function Evidence.' It also states important scope boundaries (no managed code execution, no metadata-token-to-native-address translation). However, it does not explicitly distinguish this tool from the sibling 'inspect_managed_native_boundaries', so the purpose is clear but not fully differentiated.

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?

There is no explicit guidance about when to use this tool versus alternatives such as 'inspect_managed_native_boundaries' or the other verify_* tools. The verb 'Verify' implies usage, but the definition leaves the agent to infer the selection context. No when-not-to-use conditions or alternative routing are provided.

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