Skip to main content
Glama

Oria CRM

by com.realoria
OverviewDiscussionsAdmin

List contacts

list_contacts
Read-onlyIdempotent

Search this agency's contacts by name/email/phone, optionally filtered by kind, status or tag. Returns ids you can use with other tools.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qNoFree-text search over name, email, phone.
tagNoOnly contacts with this tag.
kindNo
limitNo
sourceNoOnly contacts who first came from this channel ('import' = a CSV import).
statusNo
ownerAgentIdNoOnly contacts this agent is responsible for (id from list_agents).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / status
      Added value: +{
+  "enum": [
+    "new",
+    "contacted",
+    "active",
+    "client",
+    "inactive"
+  ],
+  "type": "string"
+}
    • addedInput schema / properties / tag
      Added value: +{
+  "description": "Only contacts with this tag.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. Changed2 schema fields changed
    • changedInput schema / properties / source / description
      Previous value: -"Only contacts who first came from this channel."New value: +"Only contacts who first came from this channel ('import' = a CSV import)."
    • changedInput schema / properties / source / enum
      Previous value: -[
-  "manual",
-  "website",
-  "storia",
-  "imobiliare",
-  "auction"
-]New value: +[
+  "manual",
+  "website",
+  "storia",
+  "imobiliare",
+  "auction",
+  "import"
+]
  3. Changed1 schema field changed
    • addedInput schema / properties / source
      Added value: +{
+  "description": "Only contacts who first came from this channel.",
+  "enum": [
+    "manual",
+    "website",
+    "storia",
+    "imobiliare",
+    "auction"
+  ],
+  "type": "string"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / ownerAgentId
      Added value: +{
+  "description": "Only contacts this agent is responsible for (id from list_agents).",
+  "format": "uuid",
+  "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$",
+  "type": "string"
+}
  5. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is well covered. The description adds useful context: that results are ids usable with other tools, and that filtering is optional (all params optional). It does not discuss pagination or limit behavior, which would be welcome but is a smaller gap given the annotations.

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?

Two concise sentences, front-loaded with the core action and scope, followed by the output-value note. No filler, no repetition of schema.

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?

For an unauthenticated, read-only list/search with no output schema, the description provides adequate context: what is searched, what filters are available, and what ids can be used for. It could note default limit or pagination behavior, but overall it is complete enough for correct invocation.

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 57%. The description covers the main search fields (name/email/phone) and mentions kind/status/tag filters, matching several schema parameters. But it omits source, limit, and ownerAgentId, and does not explain the q parameter's max length or search scope. Baseline 3 is appropriate when the schema covers a good portion but description only partially compensates.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb+resource ('Search this agency's contacts') and names the exact search fields (name/email/phone). It also distinguishes the output role ('returns ids you can use with other tools'), which separates it from get_contact. This is a clear, specific purpose.

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?

The description implies a search/list context and mentions optional filters, but offers no explicit when-to-use versus siblings like get_contact, match_contacts_to_property, or search. The agent must infer that this is a broad lookup rather than a targeted fetch.

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

All Oria CRM toolsInspect
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