Skip to main content
Glama
Sign In

AskRentAI

by com.askrentai
OverviewDiscussionsAdmin

Lead Source Summary

lead_source_summary
Read-onlyIdempotent

LEAD SOURCE BREAKDOWN — counts of prospects by lead source for a property or portfolio over a date window.

Answers "lead sources", "lead source breakdown", "where are prospects coming from", "marketing channel ROI", "how did this park's leads find us", etc. One call returns the full breakdown across all prospects in scope (get_prospect returns a single prospect).

Args: start_date: YYYY-MM-DD. Defaults to 90 days ago when omitted. end_date: YYYY-MM-DD. Defaults to today when omitted. property_id / shortname / portfolio / property_ids: scope.

``location`` (optional): a Rent Manager Location ID, a comma-separated
list, or ``"all"`` to run across every Location on this connection (see
``list_locations``). Blank = all Locations if the connection has several,
else its only Location. Output is labelled per Location; a Location that
can't be reached is listed as skipped. IDs (property, tenant, ...) belong
to one Location, so pass that Location when you filter by one.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lead_source_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_dateNo
locationNo
portfolioNo
shortnameNo
start_dateNo
property_idNo
property_idsNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / location
      Added value: +{
+  "default": "",
+  "title": "Location",
+  "type": "string"
+}
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the description is free to add the operationally important details it does: default date windows (90 days / today), per-Location output labelling, skipped Locations reported rather than silently dropped, and the constraint that IDs belong to one Location so the matching Location must be passed when filtering by ID.

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?

Well front-loaded with a header, then usage phrases, then an Args block — easy to scan. The list of example queries is slightly padded and the unlabeled 'location' paragraph sits apart from the Args block rather than with the other parameters, costing a little cohesion.

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?

An output schema exists, so return structure needn't be described, and the annotations carry the safety profile. Given that, nothing an agent needs to invoke this correctly — scope resolution, date defaults, multi-Location behavior, filtered-ID caveat — is missing.

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

Parameters5/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, and it does: it documents date formats and defaults, names all four scope parameters (property_id / shortname / portfolio / property_ids), and gives location rich semantics (single ID, comma list, or 'all', plus the blank-default behavior). Only type information is left to the schema.

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?

Opens with a specific verb+resource ('LEAD SOURCE BREAKDOWN — counts of prospects by lead source') and states the scope (property/portfolio over a date window). It also distinguishes itself from the nearest sibling by noting that get_prospect returns a single prospect while this returns the full breakdown.

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?

Provides concrete triggering phrases ('where are prospects coming from', 'marketing channel ROI') and explicitly contrasts with get_prospect for single-record lookup. It does not, however, address the other adjacent siblings (list_prospects, analyze_prospect_pipeline, analyze_lost_prospects), so the agent must infer boundaries there.

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

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