Pylon MCP Server

pylon_search_accounts

Search customer accounts using filters like name, domains, tags, or external IDs. Returns a compact table for quick review.

Instructions

Search accounts with filters. Returns compact table.

Input Schema

TableJSON Schema

Name	Required	Description
`filter`	Yes	Filter object. Each field requires an operator like {name: {string_contains: "acme"}}
`limit`	No	Results limit (1-100, default 50)
`cursor`	No	Pagination cursor

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedv1.0.1May 7, 2026
- removedInput schema / properties / filter / additionalProperties
```
Removed value: -{}
```
- changedInput schema / properties / filter / description
```
Previous value: -"Filter object with fields like domains, tags, name. Supports operators: equals, contains, in, not_in, is_set, is_unset"New value: +"Filter object. Each field requires an operator like {name: {string_contains: \"acme\"}}"
```
- addedInput schema / properties / filter / properties / domains / description
```
Added value: +"Filter by domains"
```
- addedInput schema / properties / filter / properties / domains / properties / contains
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / domains / properties / does_not_contain
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / external_ids / description
```
Added value: +"Filter by external IDs"
```
- addedInput schema / properties / filter / properties / external_ids / properties / equals
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / external_ids / properties / in
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedInput schema / properties / filter / properties / external_ids / properties / is_set
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / filter / properties / external_ids / properties / is_unset
```
Added value: +{
+  "type": "boolean"
+}
```
- addedInput schema / properties / filter / properties / external_ids / properties / not_in
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedInput schema / properties / filter / properties / name / description
```
Added value: +"Filter by account name"
```
- addedInput schema / properties / filter / properties / name / properties / equals
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / name / properties / string_contains
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / tags / description
```
Added value: +"Filter by tags"
```
- addedInput schema / properties / filter / properties / tags / properties / contains
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / tags / properties / does_not_contain
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / filter / properties / tags / properties / in
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- addedInput schema / properties / filter / properties / tags / properties / not_in
```
Added value: +{
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}
```
- changedInput schema / properties / limit / description
```
Previous value: -"Results limit"New value: +"Results limit (1-100, default 50)"
```
- changedInput schema / properties / limit / maximum
```
Previous value: -1000New value: +100
```
First observedv1.0.0Dec 14, 2025

TDQS

C2.9/5.0

Behavior2/5

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

No annotations exist, and the description only mentions 'Returns compact table' without detailing read-only nature, pagination behavior, or other traits.

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 very short and to the point, with no unnecessary words.

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?

Given no output schema, the description should explain what the compact table contains. It also lacks context on pagination and differentiation from similar tools.

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%, so the description adds no extra parameter meaning beyond the schema, meeting the baseline.

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 the verb 'search' and the resource 'accounts', and mentions filters. However, it does not differentiate from siblings like pylon_list_accounts or pylon_get_account.

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 is provided on when to use this tool versus alternatives such as pylon_list_accounts or pylon_get_account.

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

pylon_search_accounts

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools