Skip to main content
Glama

Jid: the trust API for AI agents

by com.jid
OverviewDiscussionsAdmin

Search businesses

search_business
Read-onlyIdempotent

Finds Jid business files by name or by any registry number (FEI, LEI, SEC CIK, DUNS, NDC labeler code, state licence or entity number, French SIREN or SIRET). Returns candidate files with status and match evidence. For a French company pass country "FR": the SIRENE register is searched live and files are created on demand.

Input Schema

NameRequiredDescriptionDefault
queryYesBusiness name or registry number
countryNoISO country code. "FR" also searches the French SIRENE register live (a SIREN or SIRET is looked up there anyway).

Output Schema

NameRequiredDescriptionDefault
nextYes
queryYes
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / country
      Added value: +{
+  "description": "ISO country code. \"FR\" also searches the French SIRENE register live (a SIREN or SIRET is looked up there anyway).",
+  "maxLength": 2,
+  "minLength": 2,
+  "type": "string"
+}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": {},
+  "properties": {
+    "next": {
+      "type": "string"
+    },
+    "query": {
+      "type": "string"
+    },
+    "results": {
+      "items": {
+        "additionalProperties": {},
+        "properties": {
+          "facts": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Jid file id for verify_business / get_business_file",
+            "type": "string"
+          },
+          "location": {
+            "type": "string"
+          },
+          "matched_on": {},
+          "name": {
+            "type": "string"
+          },
+          "sources": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "status": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "status_summary": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "url": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "location",
+          "status",
+          "url"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "query",
+    "results",
+    "next"
+  ],
+  "type": "object"
+}
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With annotations already covering the read-only/idempotent safety profile, the description adds real behavioral context: results are candidates with status and match evidence, and FR searches hit the live SIRENE register with files created on demand. Minor tension exists with readOnlyHint since on-demand file creation is a side effect, but the tool remains non-destructive and idempotent from the caller's view.

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?

Three tight sentences that front-load purpose, then result shape, then the FR special case; every sentence carries information. It loses a point for re-stating the SIRENE/FR behavior already present in the country parameter's schema description.

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

Completeness5/5

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

For a two-parameter search tool with an output schema, the description covers purpose, accepted identifier types, result shape, and the one non-obvious behavioral branch (live FR lookup with file creation). Nothing material is missing 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 description coverage is 100% and both parameters are fully documented in the schema, including the FR/SIRENE nuance. The description largely restates that same FR detail rather than adding new meaning about query format (e.g., normalization, partial matching), so baseline 3 applies.

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 states a specific verb and resource ('Finds Jid business files') and enumerates the identifier types it accepts (FEI, LEI, SEC CIK, DUNS, NDC, SIREN/SIRET), which makes the scope concrete. It does not, however, explicitly differentiate itself from siblings like get_business_file or verify_business, leaving that distinction to be inferred.

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?

There is one actionable usage rule ('For a French company pass country "FR"'), which tells the agent how to trigger live SIRENE lookup. Beyond that, no guidance is given on when to search here versus calling get_business_file or verify_business, and no exclusions or prerequisites are stated.

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

All Jid: the trust API for AI agents 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