CFO+

find_activity

Read-onlyIdempotent

Find the CFO+ activity (of 138, in 11 sectors) that matches a business description, e.g. "عيادة أسنان" or "coffee shop". Returns keys to use with activity_details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "find_activity"
  }
}

Input Schema

Name	Required	Default
`lang`	No	ar
`limit`	No
`query`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety needs no restating. The description adds genuinely useful context beyond that: the finite dataset size, the fact that only keys are returned rather than full records, and example inputs. It still doesn't disclose match semantics (partial vs exact, Arabic normalization) or no-match behavior.

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?

Two short sentences, front-loaded with the core action and immediately followed by the chaining hint. Minor cost: "CFO+" is unexplained internal jargon that adds no information for the agent.

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

Completeness3/5

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

For a 3-parameter lookup with no output schema, the description covers purpose and return shape adequately. It falls short on two of three parameters and on the failure mode (no match), which an agent needs to interpret an empty result set correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry the parameter burden, but it only illustrates the required `query` argument. The `lang` parameter (default "ar") and `limit` (default 5) are never mentioned, leaving their effect on results and result count undocumented.

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?

States a specific verb and resource ("Find the ... activity") plus the scope (138 activities across 11 sectors) and gives concrete query examples in two languages. It also distinguishes itself from activity_details by explaining that the output is keys for that tool, so an agent can tell the two apart without opening either schema.

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 chaining instruction ("Returns keys to use with activity_details") makes the intended workflow clear: this is the lookup step before retrieving details. What's missing is any exclusion or edge-case guidance — no statement about what to do when no activity matches, or whether this is fuzzy or exact matching.

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

All CFO+ 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?