Skip to main content
Glama

Private Blind Lookup

private_blind_lookup
Read-only

Blind proxy removes the target from x402 facilitator metadata; HirePulse and the destination still see it. Arguments are tool and target only. $0.02 single check; $0.04 company_profile/due_diligence bundle via X-Private-Query-Tier or MCP metadata hirepulse/private-tier. Direct tools suit non-private lookups.

Input Schema

NameRequiredDescriptionDefault
toolYesLookup to execute. company_profile and due_diligence require the bundle tier selected in the HTTP header or MCP request metadata.
targetYesBare public domain for company tools, or a public HTTP(S) URL for clean_markdown; excluded from facilitator metadata, but visible to HirePulse and the destination.

Output Schema

NameRequiredDescriptionDefault
codeNo
domainNo
resultNo
statusNo
sandboxNo
privacy_guaranteeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedOutput schema / anyOf
      Removed value: -[
      -  {
      -    "properties": {
      -      "domain": {
      -        "type": "string"
      -      },
      -      "privacy_guarantee": {
      -        "type": "string"
      -      },
      -      "result": {
      -        "type": "object"
      -      },
      -      "sandbox": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "demo_domain": {
      -            "const": true,
      -            "type": "boolean"
      -          },
      -          "note": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "demo_domain",
      -          "note"
      -        ],
      -        "type": "object"
      -      },
      -      "status": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "domain",
      -      "status"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": true,
      -    "properties": {
      -      "code": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "status": {
      -        "maximum": 599,
      -        "minimum": 400,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "status",
      -      "code"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedOutput schema / description
      Added value: +"Fields only; full schema in GET /v1/catalog."
    • addedOutput schema / properties
      Added value: +{
      +  "code": {},
      +  "domain": {},
      +  "privacy_guarantee": {},
      +  "result": {},
      +  "sandbox": {},
      +  "status": {}
      +}
  2. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "properties": {
      +      "domain": {
      +        "type": "string"
      +      },
      +      "privacy_guarantee": {
      +        "type": "string"
      +      },
      +      "result": {
      +        "type": "object"
      +      },
      +      "sandbox": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "demo_domain": {
      +            "const": true,
      +            "type": "boolean"
      +          },
      +          "note": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "demo_domain",
      +          "note"
      +        ],
      +        "type": "object"
      +      },
      +      "status": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "domain",
      +      "status"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "code": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "status": {
      +        "maximum": 599,
      +        "minimum": 400,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "status",
      +      "code"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / description
      Removed value: -"Fields only; full schema in GET /v1/catalog."
    • removedOutput schema / properties
      Removed value: -{
      -  "code": {},
      -  "domain": {},
      -  "privacy_guarantee": {},
      -  "result": {},
      -  "sandbox": {},
      -  "status": {}
      -}
  3. Changed3 schema fields changed
    • removedOutput schema / anyOf
      Removed value: -[
      -  {
      -    "properties": {
      -      "domain": {
      -        "type": "string"
      -      },
      -      "privacy_guarantee": {
      -        "type": "string"
      -      },
      -      "result": {
      -        "type": "object"
      -      },
      -      "sandbox": {
      -        "additionalProperties": false,
      -        "properties": {
      -          "demo_domain": {
      -            "const": true,
      -            "type": "boolean"
      -          },
      -          "note": {
      -            "type": "string"
      -          }
      -        },
      -        "required": [
      -          "demo_domain",
      -          "note"
      -        ],
      -        "type": "object"
      -      },
      -      "status": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "domain",
      -      "status"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": true,
      -    "properties": {
      -      "code": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "status": {
      -        "maximum": 599,
      -        "minimum": 400,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "status",
      -      "code"
      -    ],
      -    "type": "object"
      -  }
      -]
    • addedOutput schema / description
      Added value: +"Fields only; full schema in GET /v1/catalog."
    • addedOutput schema / properties
      Added value: +{
      +  "code": {},
      +  "domain": {},
      +  "privacy_guarantee": {},
      +  "result": {},
      +  "sandbox": {},
      +  "status": {}
      +}
  4. Changed1 schema field changed
    • changedOutput schema / anyOf
      Previous value: -[
      -  {
      -    "properties": {
      -      "domain": {
      -        "type": "string"
      -      },
      -      "privacy_guarantee": {
      -        "type": "string"
      -      },
      -      "result": {
      -        "type": "object"
      -      },
      -      "status": {
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "domain",
      -      "status"
      -    ],
      -    "type": "object"
      -  },
      -  {
      -    "additionalProperties": true,
      -    "properties": {
      -      "code": {
      -        "minLength": 1,
      -        "type": "string"
      -      },
      -      "status": {
      -        "maximum": 599,
      -        "minimum": 400,
      -        "type": "integer"
      -      }
      -    },
      -    "required": [
      -      "status",
      -      "code"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "properties": {
      +      "domain": {
      +        "type": "string"
      +      },
      +      "privacy_guarantee": {
      +        "type": "string"
      +      },
      +      "result": {
      +        "type": "object"
      +      },
      +      "sandbox": {
      +        "additionalProperties": false,
      +        "properties": {
      +          "demo_domain": {
      +            "const": true,
      +            "type": "boolean"
      +          },
      +          "note": {
      +            "type": "string"
      +          }
      +        },
      +        "required": [
      +          "demo_domain",
      +          "note"
      +        ],
      +        "type": "object"
      +      },
      +      "status": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "domain",
      +      "status"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "code": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "status": {
      +        "maximum": 599,
      +        "minimum": 400,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "status",
      +      "code"
      +    ],
      +    "type": "object"
      +  }
      +]
  5. Changed3 schema fields changed
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "properties": {
      +      "domain": {
      +        "type": "string"
      +      },
      +      "privacy_guarantee": {
      +        "type": "string"
      +      },
      +      "result": {
      +        "type": "object"
      +      },
      +      "status": {
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "domain",
      +      "status"
      +    ],
      +    "type": "object"
      +  },
      +  {
      +    "additionalProperties": true,
      +    "properties": {
      +      "code": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "status": {
      +        "maximum": 599,
      +        "minimum": 400,
      +        "type": "integer"
      +      }
      +    },
      +    "required": [
      +      "status",
      +      "code"
      +    ],
      +    "type": "object"
      +  }
      +]
    • removedOutput schema / properties
      Removed value: -{
      -  "domain": {
      -    "type": "string"
      -  },
      -  "privacy_guarantee": {
      -    "type": "string"
      -  },
      -  "result": {
      -    "type": "object"
      -  },
      -  "status": {
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / required
      Removed value: -[
      -  "domain",
      -  "status"
      -]
  6. Changed2 schema fields changed
    • addedInput schema / properties / target / description
      Added value: +"Bare public domain for company tools, or a public HTTP(S) URL for clean_markdown; excluded from facilitator metadata, but visible to HirePulse and the destination."
    • addedInput schema / properties / tool / description
      Added value: +"Lookup to execute. company_profile and due_diligence require the bundle tier selected in the HTTP header or MCP request metadata."
  7. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The description adds substantial behavior beyond the readOnly/openWorld annotations: precisely what the privacy envelope hides (facilitator metadata) and what it does not hide (HirePulse and the destination still see the target), plus per-call pricing ($0.02 / $0.04) and the header/metadata key used to select the bundle tier. What it omits is the payment mechanics and what happens when bundle-tier tools are requested without a tier selected, which matters for a paid proxy.

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?

Short and front-loaded – the privacy claim leads, pricing and tier mechanics follow, and the alternative routing closes. Every sentence carries information, but the telegraphic, semicolon-chained style makes the opening clause easy to misparse on a first read.

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 only two fully documented parameters and an output schema covering return values, the description supplies the remaining decision-critical context: privacy scope, cost, and tier routing. The main residual gap is the payment/auth precondition for an x402 proxy call, which an agent needs to know before invoking.

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 description coverage is 100%, and the schema already documents the domain-vs-URL distinction for target and the bundle-tier requirement in the tool enum, so the burden is low. 'Arguments are tool and target only' largely restates the schema rather than adding new semantics. Baseline 3 is appropriate.

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 conveys that this is a blind proxy that executes one of a set of lookups while stripping the target from x402 facilitator metadata, and the schema enum makes the lookup set concrete. However, it never states the action in a plain verb+resource form (e.g., 'run a lookup privately'), so the purpose must be inferred from 'Blind proxy removes the target...'. It does successfully distinguish itself from the direct lookup tools by name category.

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

Usage Guidelines4/5

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

The closing line 'Direct tools suit non-private lookups' explicitly routes the agent: use this when privacy is required, use direct tools otherwise. It also flags that company_profile/due_diligence require the bundle tier to be selected first. It does not spell out the inverse condition ('use this only when the target is sensitive') as sharply as it could, but the when/when-not contrast is present.

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.