PHION Agent Trust Infrastructure

contact_enrichment_evidence

Business-contact enrichment with free input preflight, identity limitations and signed receipt; 0.007 USDC.

Input Schema

TableJSON Schema

Name	Required	Description
`lid`	No
`name`	No
`email`	No
`input`	No
`phone`	No
`query`	No
`entity`	No
`pdl_id`	No
`person`	No
`region`	No
`school`	No
`ticker`	No
`company`	No	Company name or nested input object
`contact`	No
`country`	No
`profile`	No
`subject`	No
`website`	No
`locality`	No
`location`	No
`last_name`	No
`birth_date`	No
`email_hash`	No
`first_name`	No
`identifier`	No	Email, profile URL, phone, company domain, ticker or name; interpreted by service
`postal_code`	No
`street_address`	No
`minimum_likelihood`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed28 schema fields changedSep 19, 2026

addedInput schema / additionalProperties
```
Added value: +true
```

removedInput schema / anyOf

Removed value: -[
-  {
-    "required": [
-      "email"
-    ]
-  },
-  {
-    "required": [
-      "profile"
-    ]
-  },
-  {
-    "required": [
-      "name",
-      "company"
-    ]
-  }
-]

addedInput schema / description

Added value: +"Person identifier: pdl_id, email, email_hash, phone, lid, profile, or name plus context; nested input/query/subject/person/contact accepted. Validation occurs before payment."

addedInput schema / minProperties
```
Added value: +1
```
addedInput schema / properties / birth_date
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / company / description

Added value: +"Company name or nested input object"

removedInput schema / properties / company / type
```
Removed value: -"string"
```
addedInput schema / properties / contact
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / country
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / email_hash
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / entity
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / first_name
```
Added value: +{
+  "type": "string"
+}
```

addedInput schema / properties / identifier

Added value: +{
+  "description": "Email, profile URL, phone, company domain, ticker or name; interpreted by service",
+  "type": "string"
+}

addedInput schema / properties / input
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / last_name
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / lid
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / locality
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / pdl_id
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / person
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / phone
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / postal_code
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / query
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / region
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / school
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / street_address
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / subject
```
Added value: +{
+  "type": "object"
+}
```
addedInput schema / properties / ticker
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / website
```
Added value: +{
+  "type": "string"
+}
```

AddedSep 15, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose useful behavioral traits: free input preflight, identity limitations, signed receipt, and the 0.007 USDC cost. But it omits whether the operation is read-only, what the signed receipt contains, and possible failure modes.

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 tight sentence, front-loading the core purpose and packing cost, preflight, and identity constraints without filler. It could be slightly better structured, but it earns its brevity.

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

Completeness2/5

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

For a tool with 28 parameters, no output schema, and no annotations, one line is insufficient. An agent cannot determine which identifier to pass, what the signed receipt looks like, or how identity limitations affect the enrichment result.

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 only 7%, yet the description names no parameters and gives no guidance on the 28 inputs. It only implies the input is a business contact, which does little to clarify how to populate fields like lid, pdl_id, query, or subject.

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 clearly states 'Business-contact enrichment' – a specific verb and resource – and the 'business-contact' qualifier helps distinguish it from company or person enrichment siblings. However, it does not name any sibling or explicitly state what the evidence output looks like.

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 usage context or alternatives are provided. The description mentions preflight and identity limitations but never says when to use this tool over company_enrichment_evidence, person_enrichment_evidence, or entity_enrichment_evidence.

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

All PHION Agent Trust Infrastructure tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?