Skip to main content
Glama

B2B Lead Enrichment, SaaS Tech Stack, ATS Jobs & SEC Form D MCP

Search NetSuite SuiteApp ERP Partners

search_netsuite_erp_partners
Read-onlyIdempotent

Searches the 724 verified Oracle NetSuite SuiteApp ERP software partners (ISVs), Built-for-NetSuite badges, and SuiteApp URLs.

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": "search_netsuite_erp_partners"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to preview (1 to 25, default 10)
queryNoOptional keyword such as AI, tax, warehouse, billing, or EDI

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety and idempotency are covered structurally. The description adds genuine context beyond that: the corpus size (724 verified partners) and the fact that badge status and SuiteApp URLs are part of the data. It does not disclose result shape, ordering, or that results are a preview rather than the full set.

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?

A single front-loaded sentence with no filler or repetition; the scope qualifier and data types are stated up front. Slightly dense with the parenthetical "(ISVs)" and the long modifier chain, but nothing is wasted.

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 a two-parameter, all-optional read-only search with rich annotations, the description covers the domain, the corpus, and the notable data fields. Since no output schema exists, a brief note on what a result row looks like would have closed the last gap, but an agent has enough to invoke it correctly.

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%, so both parameters are already documented with types, bounds, and example keywords. The description adds nothing about how query matching works (substring vs. token, which fields are searched) or what limit truncation means for completeness. Baseline 3 applies when the schema carries the parameter burden.

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 uses a specific verb ("Searches") and a precisely scoped resource: the 724 verified Oracle NetSuite SuiteApp ERP partners, plus the badge and URL data attached to them. It also implicitly reveals the domain boundary (NetSuite SuiteApp ISVs), which is enough to separate it from the unrelated siblings like extract_ats_hiring_signals or qualify_b2b_lead. It falls short of a 5 only because it never states what a returned row actually contains.

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?

Usage is implied by the name and the search framing, but there is no explicit when-to-use, when-not-to-use, or alternative named. An agent can infer this is the lookup tool for NetSuite partners, but nothing tells it whether an empty query returns all 724 records or how it relates to any other lookup path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.