Skip to main content
Glama

Civify

by cv.civify.mcp
OverviewDiscussionsAdmin

Get Pay-Per-CV Pricing

civify_get_pay_per_cv_pricing
Read-onlyIdempotent

Get public localized Pay-Per-CV pricing (USD base price, converted EGP regional pricing, exchange rates, and entitlement details). Public, no auth required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • removedOutput schema / properties / currency
      Removed value: -{
-  "description": "Default base currency (USD)",
-  "type": "string"
-}
    • addedOutput schema / properties / data
      Added value: +{}
    • removedOutput schema / properties / exchangeRate
      Removed value: -{
-  "description": "Current currency exchange rate applied",
-  "type": "number"
-}
    • removedOutput schema / properties / products
      Removed value: -{
-  "description": "Available Pay-Per-CV packages",
-  "items": {
-    "properties": {
-      "features": {
-        "description": "List of included package features and benefits",
-        "items": {
-          "type": "string"
-        },
-        "type": "array"
-      },
-      "id": {
-        "description": "Product ID (PAY_PER_CV_SINGLE or PAY_PER_CV_PACK3)",
-        "type": "string"
-      },
-      "name": {
-        "description": "Product display name",
-        "type": "string"
-      },
-      "priceRegional": {
-        "description": "Converted regional price in localized currency",
-        "type": "number"
-      },
-      "priceUsd": {
-        "description": "Base price in USD",
-        "type": "number"
-      }
-    },
-    "required": [
-      "id",
-      "priceUsd"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedOutput schema / properties / regionalCurrency
      Removed value: -{
-  "description": "Localized currency detected from GeoIP (e.g. EGP)",
-  "type": "string"
-}
    • changedOutput schema / required
      Previous value: -[
-  "currency",
-  "products"
-]New value: +[
+  "data"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds value by specifying 'Public, no auth required' (not in annotations) and detailing the exact data returned (pricing, exchange rates, entitlement details). It does not contradict annotations and supplements them with useful behavioral context.

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?

The description is a single, front-loaded sentence that immediately states the tool's purpose and then lists specifics. Every phrase adds value—'public localized', 'USD base price, converted EGP regional pricing, exchange rates, and entitlement details'—without waste. It is highly concise and well-structured.

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?

Given the tool's simplicity (no parameters) and the presence of an output schema that documents return format, the description fully covers what an agent needs: purpose, public nature, and the specific data contents. Nothing essential is missing.

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

Parameters4/5

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

The tool has zero parameters, so the baseline is 4. The description mentions the type of information returned but doesn't need to elaborate on parameters since none exist. No gaps here.

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 clearly states the tool retrieves public localized Pay-Per-CV pricing, enumerating specific contents (USD base, EGP pricing, exchange rates, entitlement details). It uses a specific verb 'Get' with a precise resource, and the public scope distinguishes it from other tools. It avoids tautology and is unambiguous.

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 description provides clear context: 'Public, no auth required' tells when this tool is appropriate (public access, no authentication needed). It does not explicitly mention alternatives or exclusions, such as noting that entitlement details could also be checked via a sibling tool like civify_check_cv_entitlement, but the context is sufficient for basic routing.

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

All Civify 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